Re: Documentation Update: Document pg_start_backup checkpoint behavior

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "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>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: Documentation Update: Document pg_start_backup checkpoint behavior
Date: 2009-04-06 20:21:49
Message-ID: 49DA1E0D.EE98.0025.0@wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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?)

-Kevin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-04-06 20:30:25 Re: Documentation Update: Document pg_start_backup checkpoint behavior
Previous Message Tom Lane 2009-04-06 20:07:26 Re: Documentation Update: Document pg_start_backup checkpoint behavior