Re: Documentation Update: Document pg_start_backup checkpoint behavior

From: Bernd Helmle <mailings(at)oopsware(dot)de>
To: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Michael Renner <michael(dot)renner(at)amd(dot)co(dot)at>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Documentation Update: Document pg_start_backup checkpoint behavior
Date: 2009-04-03 15:39:30
Message-ID: 0C4B9F71BAE17481AD6B6029@teje
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

--On Freitag, April 03, 2009 08:30:14 +0300 Heikki Linnakangas
<heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:

> The first looks nicer, IMHO, because the word 'lazy' makes it
> self-documenting. In the second form, you have to look at the manual to
> figure out what the 2nd argument does.

Regarding that many catalog functions are already overloaded and in the
name of consistency i vote for your 2nd argument.

--
Thanks

Bernd

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2009-04-03 15:45:55 Re: a few crazy ideas about hash joins
Previous Message Tom Lane 2009-04-03 15:38:03 Re: Crash in gist insertion on pathological box data