| From: | Alban Hertroys <alban(at)magproductions(dot)nl> |
|---|---|
| To: | "Ed L(dot)" <pgsql(at)bluepolka(dot)net> |
| Cc: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>, Postgres-General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Converting non-null unique idx to pkey |
| Date: | 2007-08-23 08:23:04 |
| Message-ID: | 46CD43E8.90900@magproductions.nl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Ed L. wrote:
> On Tuesday 21 August 2007 1:45 pm, Scott Marlowe wrote:
>> If you have a large db in 7.4.6, you should do two things.
>>
>> 1: Update to 7.4.19 or whatever the latest flavor of 7.4 is,
>> right now. There are a few known data eating bugs in 7.4.6.
>
> Sounds like good advice from a strictly technical viewpoint.
> Unfortunately, in our particular real world, there are also
> political, financial, and resource constraints and impacts from
> downtime that at times outweigh the technical merits of
> upgrading 'right now'.
Since you're setting up replication to another database, you might as
well try replicating to a newer release and swap them around once it's
done. I've seen that method of upgrading mentioned on this list a few times.
--
Alban Hertroys
alban(at)magproductions(dot)nl
magproductions b.v.
T: ++31(0)534346874
F: ++31(0)534346876
M:
I: www.magproductions.nl
A: Postbus 416
7500 AK Enschede
// Integrate Your World //
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hannes Dorbath | 2007-08-23 08:24:32 | Re: CPU load high |
| Previous Message | Kristo Kaiv | 2007-08-23 08:16:33 | Re: table column vs. out param [1:0] |