"Andrew Janian" <ajanian@scottrade.com> writes:
> I am experiencing a similar problem with PostgreSQL running on Debian.
> I am not doing anything special when it happens, just once and a
> while. It is not a production system (on which this problem does not
> occur) so I just restart and everything is fine.
Restart? Do you actually need to restart to make the problem stop?
If so, do you mean restarting the PG postmaster, or rebooting the whole
machine? Would maybe just starting a fresh backend (psql session) make
the problem stop?
regards, tom lane
