Re: Documentation Update: Document pg_start_backup checkpoint behavior - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Documentation Update: Document pg_start_backup checkpoint behavior
Date
Msg-id 27334.1238765245@sss.pgh.pa.us
Whole thread Raw
In response to Re: Documentation Update: Document pg_start_backup checkpoint behavior  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: Documentation Update: Document pg_start_backup checkpoint behavior  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> writes:
> Rather than deplore that you can't expedite the checkpoint, why don't we 
> just make it possible?

+1

> The first question is what the default behavior should be? We've seen 
> enough complaints and I've been bitten by that myself during development 
> of other stuff often enough that I think we should change the default to 
> immediate. From backwards-compatibility point of view, we shouldn't 
> change the default, but then again an immediate checkpoint was what you 
> got before 8.3.

I think we shouldn't change the default.  Which puts a hole in your
suggestion for function naming.  But then again, I like the extra
argument better anyway ...
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Documentation Update: Document pg_start_backup checkpoint behavior
Next
From: Kenneth Marshall
Date:
Subject: Re: a few crazy ideas about hash joins