Re: Proposed patch for LISTEN/NOTIFY race condition

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-patches(at)postgreSQL(dot)org, Laurent Birtz <laurent(dot)birtz(at)kryptiva(dot)com>
Subject: Re: Proposed patch for LISTEN/NOTIFY race condition
Date: 2008-03-12 13:12:33
Message-ID: 20080312131233.GD4926@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Tom Lane wrote:

> The patch disallows LISTEN/NOTIFY in a prepared transaction, and there
> is also a side effect on whether a transaction can see entries in
> pg_listener for its own uncommitted LISTEN commands.

I wonder if it would've been easier to make NOTIFY use SnapshotDirty to
examine pg_listener, thus causing it to see the uncommitted rows. Would
that work at all?

--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Heikki Linnakangas 2008-03-12 13:43:46 Re: [PERFORM] Very slow (2 tuples/second) sequential scan after bulk insert; speed returns to ~500 tuples/second after commit
Previous Message Bruce Momjian 2008-03-12 13:11:48 Re: BUG #3681: fillers are NULL in pgbench