Re: Re: [COMMITTERS] pgsql: Tune GetSnapshotData() during Hot Standby by avoiding loop

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Re: [COMMITTERS] pgsql: Tune GetSnapshotData() during Hot Standby by avoiding loop
Date: 2010-04-19 14:24:28
Message-ID: 13439.1271687068@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Mon, Apr 19, 2010 at 5:05 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
>> It doesn't seem to be something we should place highly on the list of
>> events we need protection from, does it?

> Since when do we not protect against race-conditions just because
> they're low likelihood?

Murphy's law says that the probability of any race condition happening
in the field is orders of magnitude higher than you think. This has
been proven true many times ...

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Simon Riggs 2010-04-19 14:31:29 Re: Re: [COMMITTERS] pgsql: Tune GetSnapshotData() during Hot Standby by avoiding loop
Previous Message Magnus Hagander 2010-04-19 14:10:45 pgsql: Add wrapper function libpqrcv_PQexec() in the walreceiver that

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2010-04-19 14:26:26 Re: shared_buffers documentation
Previous Message Kevin Grittner 2010-04-19 14:21:17 Re: shared_buffers documentation