Re: timeout implementation issues - Mailing list pgsql-hackers

From Tom Lane
Subject Re: timeout implementation issues
Date
Msg-id 12069.1017864203@sss.pgh.pa.us
Whole thread Raw
In response to Re: timeout implementation issues  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
Bruce Momjian <pgman@candle.pha.pa.us> writes:
> Does anyone know the ramifications of allowing SET to work in an aborted
> transaction?

This is not an option.

The case that will definitely Not Work is SET variables whose setting
or checking requires database accesses.  The new search_path variable
certainly works that way; not sure if there are any other cases at the
moment, but I'd not like to say that there can never be any such
variables.
        regards, tom lane


pgsql-hackers by date:

Previous
From: "SHELTON,MICHAEL (Non-HP-Boise,ex1)"
Date:
Subject: FW: Suggestions please: names for function cachability
Next
From: Tom Lane
Date:
Subject: Re: notification: pg_notify ?