On Tue, Nov 29, 2011 at 3:37 AM, Daniel Farina <dan...@heroku.com> wrote: > Hmm, just to prod this thread: has any fix for this been committed? > After Nikhil confirmed that this bug could cause pg_dump to not be > able to operate without direct catalog surgery I have encountered this > bug (and treated its symptoms in the same manner) twice. I tried to > do my homework in a backbranch, but am not seeing anything beaming out > at me.
I have plans to try to improve this, but it's one of those things that I care about more than the people who write the checks do, so it hasn't quite gotten to the top of the priority list yet. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
