On 04/28/12 17:17, Jeff Frost wrote: > Since I had a theory that it's probably stalling on pg_catalog access, one of > the guys wrote a test harness that makes several connections and creates and > drops lots of temp tables. That does seem to allow us to reproduce the issue > in the production DB, but not in a newly created DB. So, we're about to > initdb a new data directory and slony replicate the data over to it on the > original server.
After slony replicating over to the freshly initdb'd original server, the problem has not recurred. Maybe the problem was catalog corruption? -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
