| From: | Grzegorz Jaskiewicz <gj(at)pointblue(dot)com(dot)pl> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Josh Berkus <josh(at)agliodbs(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Brad Nicholson <bnichols(at)ca(dot)afilias(dot)info>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: pg_migrator issue with contrib |
| Date: | 2009-06-07 09:02:32 |
| Message-ID: | 093489D2-D37B-4423-8EF3-0E107E64C5C3@pointblue.com.pl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 7 Jun 2009, at 03:27, Bruce Momjian wrote:
> Grzegorz Jaskiewicz wrote:
>>
>> On 6 Jun 2009, at 19:50, Tom Lane wrote:
>>> We have five days.
>>>
>>> I don't think we need testing, per se. The first step should be to
>>> diff
>>> the 8.3 and 8.4 versions of the various contrib .sql.in files and
>>> determine what changed. Any module whose .sql.in file hasn't
>>> changed
>>> is definitely safe.
>>
>> I can tell you already that dblink has changed, and I had to drop it
>> before migration, otherwise everything went fine. Migration of 57GB
>> data in place took about 1 minute.
>
> The good news is that the INSTALL instructions where clear enough for
> the tester to understand that uninstalling dblink from the old cluster
> and reinstalling it in the new cluster would work.
Yes, but I forgot about one database, and had to do it all over again,
luckily I first tested it without --link...
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2009-06-07 12:46:01 | Re: pg_migrator issue with contrib |
| Previous Message | Nicolas Barbier | 2009-06-07 07:26:29 | Re: PostgreSQL Developer meeting minutes up |