-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, 7 Jan 2008 09:18:24 -0300 Alvaro Herrera <[EMAIL PROTECTED]> wrote:
> Joshua D. Drake wrote: > > >> SELECT oid::regclass FROM pg_class WHERE > >> reltoastrelid='pg_toast.pg_toast_49013869'::regclass; > >> > >> oid | pg_temp_24.tmp_isp_blk_chk > >> > >> The hack to get this cleaned up was to connect about 2 dozen times > >> (to get to slot 24) with psql via different sessions and create > >> temp tables. Once we hit slot 24, the probably instantly went away > >> and the database returned to normal state. > > Ah -- interesting. This is a known issue, but we haven't found a > solution yet. > Is there bug number? Sincerely, 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) iD8DBQFHglltATb/zqfZUUQRAk19AJ9GywJ7ohqGZa4jrRYtufgbwCacowCgrgml 00egslWmlrI0MK2sJjyc63I= =Y4Ok -----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
