Re: BUG #6706: pg_upgrade fails when plpgsql dropped/re-created
От | Bruce Momjian |
---|---|
Тема | Re: BUG #6706: pg_upgrade fails when plpgsql dropped/re-created |
Дата | |
Msg-id | 20120705133253.GJ5578@momjian.us обсуждение исходный текст |
Ответ на | Re: BUG #6706: pg_upgrade fails when plpgsql dropped/re-created (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: BUG #6706: pg_upgrade fails when plpgsql dropped/re-created
|
Список | pgsql-bugs |
On Thu, Jul 05, 2012 at 12:21:58AM -0400, Tom Lane wrote: > Bruce Momjian <bruce@momjian.us> writes: > >>> address the points I made about reproducing the previous state in cases > >>> where the admin removed the language or changed its permissions. > > >> Well, it still does the create extension in binary mode like before --- > >> not sure what the problem is. > > > Applied and back-patched to 9.2. > > I do not believe that this patch fixes the problem, and I also believe > that it creates new problems. Please revert. I asked for an explaination of the problem, but received no reply: http://archives.postgresql.org/pgsql-bugs/2012-07/msg00005.php so I assumed you were fine with it. Please explain. Does anyone else understand the problem Tom is seeing? -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. +
В списке pgsql-bugs по дате отправления: