From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_upgrade bugs |
Date: | 2012-09-03 13:14:20 |
Message-ID: | 5044AD2C.4080308@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 09/03/2012 12:00 AM, Tom Lane wrote:
> Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
>> Maybe, to reduce future backpatching pain, we could backpatch the change
>> to exec_prog() API now that you have fixed the implementation?
> I'm inclined to think this is a good idea, but keep in mind we're less
> than four days from wrapping 9.2.0. There's not a lot of margin for
> error here.
>
> At the same time, getting pg_upgrade to pass regression on Windows would
> be a good thing, and ought to go a long way towards ameliorating worries
> about this.
My first focus was on getting it working on HEAD, and I only got there
fairly late last night.
I'll look at getting testing working on 9.2 today.
At this stage my plan is to make the absolute minimum changes necessary,
but if Alvaro wants to do something a bit larger to align t code, I'll
be happy to test it.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2012-09-03 13:15:06 | Re: [bugfix] sepgsql didn't follow the latest core API changes |
Previous Message | Magnus Hagander | 2012-09-03 11:10:47 | Re: Proof of concept: standalone backend with full FE/BE protocol |