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

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: 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 11:55:29
Message-ID: v2y603c8f071004190455gf18633fbx1a666c17c998b1a1@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

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?

...Robert

In response to

Responses

Browse pgsql-committers by date

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

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2010-04-19 12:02:32 Re: [GENERAL] trouble with to_char('L')
Previous Message Fujii Masao 2010-04-19 09:37:38 Re: walreceiver is uninterruptible on win32