Re: LISTEN considered dangerous

From: Harald Fuchs <hf0731x(at)protecting(dot)net>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: LISTEN considered dangerous
Date: 2006-08-02 12:00:09
Message-ID: pu8xm7gxfa.fsf@srv.protecting.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

In article <44D0478D(dot)3060201(at)partyticket(dot)net>,
Flemming Frandsen <ff(at)partyticket(dot)net> writes:

>> I would still expect any
>> reimplementation of notify messaging to honor the principle that a
>> LISTEN doesn't take effect till you commit.

> Naturally, the listen should not do anything at all when followed by a
> rollback.

> However if you start listening in a transaction then you should get
> all events that have happened after the snapshot that the transaction
> represents (the start of the transaction).

Here you're contradicting yourself. In your second paragraph you
state that LISTEN should get events unless later cancelled by a
ROLLBACK. How should LISTEN know if its transaction will commit or
abort?

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2006-08-02 12:45:29 Re: LISTEN considered dangerous
Previous Message Harald Armin Massa 2006-08-02 11:59:50 when do pg_temp SCHEMAS get purged?