Re: Any reason to use pg_dumpall on an idle database - Mailing list pgsql-hackers

From Zeugswetter Andreas
Subject Re: Any reason to use pg_dumpall on an idle database
Date
Msg-id 003601bfc74d$3eff6f40$f823080a@sd.spardat.at
Whole thread Raw
In response to Re: Any reason to use pg_dumpall on an idle database  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
> > I think it is a good idea to backup pg_log first, then the rest.
> > Then you should imho be safe even if load is heavy.
> > No vacuum until finished of course.
> 
> You know, that was always my assumption too, that doing pg_log first
> made things safer.  I am not sure if it is 100% safe, though.

I think there is a problem with our "big" pagesize of 8k.
If we used the system page size (usually 2 or 4k) a write with a 
concurrent read should imho not be possible. But since we need to write
2-4 system pages I am not so sure that that is atomic, thus we risc 
backing up an incompletely written pg page.

sounds like a nogo :-(
Andreas



pgsql-hackers by date:

Previous
From: "Zeugswetter Andreas"
Date:
Subject: Re: Berkeley DB...
Next
From: Olivier PRENANT
Date:
Subject: Re: Perl 5.6.0