We are currently using Postgresql 7.1.2, running on a E3500 server, OS
Solaris 2.6. We would like to upgrade to postgresql 7.2.
1) Do you all consider it stable enough now to upgrade?
2) If I understand correctly, to upgrade, step would be:
a) pg_dumpall
b) reset PGHOME t
Naomi Walker wrote:
> We are currently using Postgresql 7.1.2, running on a E3500 server, OS
> Solaris 2.6. We would like to upgrade to postgresql 7.2.
>
> 1) Do you all consider it stable enough now to upgrade?
>
> 2) If I understand correctly, to upgrade, step would be:
>
>a) pg_
> > > If so, that seems pretty drastic. I cannot imagine that once our
> > databases
> > > start getting really huge that this will last as an upgrade method. I
> > > thought we would be using pg_upgrade, but I see a note that it will not
> > > work with versions of postgres 7.1 and higher.
> >
At 01:53 PM 2/8/02 -0500, Bruce Momjian wrote:
>Naomi Walker wrote:
> > We are currently using Postgresql 7.1.2, running on a E3500 server, OS
> > Solaris 2.6. We would like to upgrade to postgresql 7.2.
> >
> > 1) Do you all consider it stable enough now to upgrade?
> >
> > 2) If I understand cor
Bruce Momjian <[EMAIL PROTECTED]> writes:
>> Bruce, are you saying I can use /contrib/pg_upgrade for my 7.1.2 to 7.2
>> upgrade?
> Yes, absolutely. At least it worked in my tests.
However, it'd be folly not to make a dump beforehand, so you can recover
if it doesn't work ...
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> >> Bruce, are you saying I can use /contrib/pg_upgrade for my 7.1.2 to 7.2
> >> upgrade?
>
> > Yes, absolutely. At least it worked in my tests.
>
> However, it'd be folly not to make a dump beforehand, so you can recover
> if it doe
Chad R. Larson wrote:
> At 11:53 AM 2/8/2002 , Bruce Momjian wrote:
> >It is in /contrib/pg_upgrade now and it does work for 7.1 upgrades,
> >though it is only lightly tested.
>
> When you say "work for 7.1 upgrades" I assume you mean like from 7.1.2 to
> 7.1.3. Is there a 7.1.2 to 7.2 version?
Hi all,
I'm upgrading from 7.1.3 to 7.2. Right now, I'm busy doing backups,
so I have a little time to think.
I'm thinking of changing some of the int8 fields into int4 fields,
since this would save about 4 bytes/record and with 25 Million
records, this is 100 MB just in the data per field, bu
Chad, hold up a bit. Bruce and I are talking, and i'm asking the same things.
At 02:27 PM 2/8/02 -0700, Chad R. Larson wrote:
>At 11:53 AM 2/8/2002 , Bruce Momjian wrote:
>>It is in /contrib/pg_upgrade now and it does work for 7.1 upgrades,
>>though it is only lightly tested.
>
>When you say "w
Chris Ruprecht <[EMAIL PROTECTED]> writes:
> The problem is, that the file which contains the pg_dump data is 2.8
> GB in size and I don't want to tackle that with an editor.
It may be too late if you already started the dump, but --- you could
easily avoid that issue by dumping schema and data
10 matches
Mail list logo
