On Thu, Dec 6, 2012 at 11:48 AM, Magnus Hagander <mag...@hagander.net> wrote: > Certainly sounds like a very similar problem. If so, the query is > simply buggy - it's just that a pg_upgrade'd environment is *much* > more likely to run into the problem than before. > > I only checked the usages of pg_shdescription. The same bug might well > exist with almost all uses of pg_description.
OK, here's a patch that should fix this, as well as Magnus' previous fix which doesn't appear to have been tested so well :-p Per; are you able to test this? Magnus; can you give it at least an eyeball review before I commit please, in case there are any thinkos in there. Thanks! -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company
fix_comments.diff
Description: Binary data
-- Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgadmin-support
