From: | Markus Schaber <schabi(at)logix-tt(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Upgrading a database dump/restore |
Date: | 2006-10-11 12:57:16 |
Message-ID: | 452CEA2C.3000809@logix-tt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi, Mark,
Mark Woodward wrote:
>> People are working it, someone even got so far as dealing with most
>> catalog upgrades. The hard part going to be making sure that even if
>> the power fails halfway through an upgrade that your data will still be
>> readable...
>
> Well, I think that any *real* DBA understands and accepts that issues like
> power failure and hardware failure create situations where "suboptimal"
> conditions exist. :-) Stopping the database and copying the pg directory
> addresses this problem, upon failure, it is a simple mv bkdir pgdir, gets
> you started again.
But when people have enough bandwith and disk space to copy the pg
directory, they also have enough to create and store a bzip2 compressed
dump of the database.
Or did I miss something?
HTH,
Markus
--
Markus Schaber | Logical Tracking&Tracing International AG
Dipl. Inf. | Software Development GIS
Fight against software patents in Europe! www.ffii.org
www.nosoftwarepatents.org
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2006-10-11 13:09:45 | hstore isexists |
Previous Message | Kai-Uwe Sattler | 2006-10-11 12:30:53 | Index Tuning Features [2] |