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. -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings