| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_upgrade libraries check |
| Date: | 2012-05-27 18:39:28 |
| Message-ID: | 26492.1338143968@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian <bruce(at)momjian(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sergey Koposov | 2012-05-27 18:45:19 | Re: 9.2beta1, parallel queries, ReleasePredicateLocks, CheckForSerializableConflictIn in the oprofile |
| Previous Message | Tom Lane | 2012-05-27 18:32:52 | Re: pg_upgrade libraries check |