Re: pg_upgrade libraries check - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pg_upgrade libraries check
Date
Msg-id 26492.1338143968@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_upgrade libraries check  (Bruce Momjian <bruce@momjian.us>)
Responses Re: pg_upgrade libraries check
List pgsql-hackers
Bruce Momjian <bruce@momjian.us> writes:
> On Sun, May 27, 2012 at 11:31:12AM -0400, Tom Lane wrote:
>> I don't recall exactly what problems drove us to make pg_upgrade do
>> what it does with extensions, but we need a different fix for them.

> Uh, pg_upgrade doesn't do anything special with extensions, so it must
> have been something people did in pg_dump.

Most of the dirty work is in pg_dump --binary_upgrade, but it's pretty
disingenuous of you to disavow responsibility for those kluges.  They
are part and parcel of pg_upgrade IMO.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pg_upgrade libraries check
Next
From: Sergey Koposov
Date:
Subject: Re: 9.2beta1, parallel queries, ReleasePredicateLocks, CheckForSerializableConflictIn in the oprofile