On Jan 5, 2007, at 10:01 PM, Tom Lane wrote:
Michael Best [EMAIL PROTECTED] writes:
Set your memory requirement too high in postgresql.conf, reload
instead
of restarting the database, it silently fails sometime later?
Yeah, wouldn't surprise me, since the reload is going to ignore any
Thomas F. O'Connell [EMAIL PROTECTED] writes:
Michael Best [EMAIL PROTECTED] writes:
Set your memory requirement too high in postgresql.conf, reload
instead of restarting the database, it silently fails sometime later?
Wait, now I'm curious. If a change in postgresql.conf that requires a
On Jan 4, 2007, at 11:24 PM, Michael Best wrote:
When I finally got the error report in the morning the database was
in this state:
$ psql dbname
dbname=# \dt
ERROR: cache lookup failed for relation 20884
Do you have your error logs, and were there any relevant errors in
them
Thomas F. O'Connell wrote:
On Jan 4, 2007, at 11:24 PM, Michael Best wrote:
When I finally got the error report in the morning the database was in
this state:
$ psql dbname
dbname=# \dt
ERROR: cache lookup failed for relation 20884
Do you have your error logs, and were there any
Michael Best [EMAIL PROTECTED] writes:
Set your memory requirement too high in postgresql.conf, reload instead
of restarting the database, it silently fails sometime later?
Yeah, wouldn't surprise me, since the reload is going to ignore any
changes related to resizing shared memory. I think
Had some database corruption problems today. Since they came on the
heels of making some minor database changes yesterday, they may or may
not be related to that. Centos 4.x, Postgresql 8.1.4
I modified the following settings and then issued a reload.I hadn't
turned up the kernel.shmmax
