Re: BUG #6706: pg_upgrade fails when plpgsql dropped/re-created

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: m(dot)sakrejda(at)gmail(dot)com, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #6706: pg_upgrade fails when plpgsql dropped/re-created
Date: 2012-06-30 03:35:15
Message-ID: 336.1341027315@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Bruce Momjian <bruce(at)momjian(dot)us> writes:
> I can't think of how to fix this. Perhaps we need to query the
> pg_extension table as of the SELECT function all.

I think you're misjudging the core of the issue. The same thing
would happen if somebody dropped and recreated the public schema.
Or anything else that we create at initdb time but allow to be
dropped.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Bruce Momjian 2012-06-30 05:00:07 Re: BUG #6706: pg_upgrade fails when plpgsql dropped/re-created
Previous Message Bruce Momjian 2012-06-30 01:54:30 Re: BUG #6706: pg_upgrade fails when plpgsql dropped/re-created