Scott Marlowe wrote:
As a followup to all this, the OP also needs to figure out why a
crashed server could cause so much corruption. This is usually the
result of hardware lying about fsync status, i.e. consumer grade
hardware pressed into service as a server.
See http://www.postgresql.org/
This is occurring In an 8.4.2 pg database, and I have noticed it in 8.3.10 as
well.
We do a lot of work with temp tables here, and over time a lot of pg_temp_[n]
schemas have appeared.
Similarly, we notice build-up of pg_toast_[n] schemas.
Is it ok to drop these if they contain no tables?
Or is
Mark Rostron writes:
> We do a lot of work with temp tables here, and over time a lot of pg_temp_[n]
> schemas have appeared.
> Similarly, we notice build-up of pg_toast_[n] schemas.
This is expected. There'll be one for each backend slot that's ever
used any temp tables.
> Is it ok to drop th