-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, 7 Jan 2008 10:37:18 -0800 Darcy Buskermolen <[EMAIL PROTECTED]> wrote:
> > 1. I had to manually vacuum because we had already hid xidStoplimit. > > > > 2. Postgres has been restarted multiple times and it made zero > > difference. > > > > E.g; PostgreSQL isn't cleaning up after itself and it isn't apparent > > when it happens. > > After a fresh start of postgres, there should be no temp tables, so > would a work around to this at least be at postmaster start to (for a > lack of a better pseudo code ) DROP SCHEMA pg_temp* CASCADE; before > coming up in interactive mode? Doing this would at least have > allowedthe manual vacuum to do what it needed and not have caused > confusion on the part of the user? Also it would have greatly reduced > the total time to resolution, and not requiring hacking the backend > to get there. > +1 Joshua D. Drake - -- The PostgreSQL Company: Since 1997, http://www.commandprompt.com/ Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240 Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate SELECT 'Training', 'Consulting' FROM vendor WHERE name = 'CMD' -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHgnQaATb/zqfZUUQRAt1qAJ4hzeNG8fzA4l5y/luNrg3eGOz5QQCfcvtZ xMuLPQSEbvG+AYfTRkEyLD0= =+Lkk -----END PGP SIGNATURE----- ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match