| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
| Cc: | "Michael Renner" <michael(dot)renner(at)amd(dot)co(dot)at>, "Heikki Linnakangas" <heikki(dot)linnakangas(at)enterprisedb(dot)com>, "Bruce Momjian" <bruce(at)momjian(dot)us>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Documentation Update: Document pg_start_backup checkpoint behavior |
| Date: | 2009-04-06 20:30:25 |
| Message-ID: | 16846.1239049825@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> I'm going to go ahead and make this happen, using the arrangement
>>
>> pg_start_backup('label') -> slow checkpoint (backwards compatible)
>> pg_start_backup('label', false) -> slow checkpoint
>> pg_start_backup('label', true) -> immediate checkpoint
> Probably a dumb question, but just to be sure: none of these functions
> will return before the checkpoint is complete, right? (In other
> words, when the function returns, it is safe to begin the base
> backup?)
Correct. The only change here is whether or not to pass the
CHECKPOINT_IMMEDIATE flag to RequestCheckpoint. We do CHECKPOINT_WAIT
in any case.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dann Corbit | 2009-04-06 20:32:07 | Windows installation service |
| Previous Message | Kevin Grittner | 2009-04-06 20:21:49 | Re: Documentation Update: Document pg_start_backup checkpoint behavior |