Search Postgresql Archives

Re: Database Corruption - last chance recovery options?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



"Thomas F. O'Connell" <tf@xxxxxxxxxxxxxx> writes:
>> Michael Best <mbest@xxxxxxxxxxxxx> 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  
> restart doesn't take effect on reload, then how could a related  
> failure manifest at all, regardless of when?

The point is that when you eventually shut down and restart the
postmaster, it'd fail then ... perhaps long after you've forgotten
about your configuration changes, so it might be a bit mystifying.

			regards, tom lane


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux