Hi PostgreSQL developers!

We just experienced a bug that gave us a serious headache until we
found the reason. When doing "psql template1" we got an error message

psql: FATAL: invalid cache id: 30

Evert Meulie found a similar problem at

http://archives.postgresql.org/pgsql...1/msg00237.php

so maybe it's the same bug, since the thread never came to a
conclusion.

I found out that activating

log_parser_stats = true
log_planner_stats = true
log_executor_stats = true
log_statement_stats = true

in postgresql.conf leads to this bug (test case attached, adapt the
$BIN variable to your postgresql bin directory and run the script). In
8.0 the server complains about an "invalid value for
log_statement_stats", and the documentation explains that the first
three and the 4th option are mutually exclusive. However, this is not
mentioned in the 7.4 docs. Can this case be handled more gracefully in
7.4? Maybe the check from 8.0 can be ported to 7.4?

Thanks and have a nice day!

Martin

--
Martin Pitt http://www.piware.de
Ubuntu Developer http://www.ubuntulinux.org
Debian Developer http://www.debian.org

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)

iD8DBQFCnt4LDecnbV4Fd/IRAkhMAJ0cQVpd8r76WvROxQ4C1VWeTa4tPwCfU3TQ
XN0svus1jC/0EZ1YdrntiEk=
=PqZZ
-----END PGP SIGNATURE-----