Re: timeout implementation issues

Jan Wieck <janwieck@yahoo.com>

From: Jan Wieck <janwieck@yahoo.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: PostgreSQL HACKERS <pgsql-hackers@postgreSQL.org>
Date: 2002-04-08T14:46:11Z
Lists: pgsql-hackers
Tom Lane wrote:
> Karel Zak <zakkr@zf.jcu.cz> writes:
> >  Is there some problem implement "SET ... ON ROLLBACK UNSET" ?
>
> Yes.  See my previous example concerning search_path: that variable
> MUST be rolled back at transaction abort, else we risk its value being
> invalid.  We cannot offer the user a choice.

    Not  really on topic, but I was wondering how you ensure that
    you correct the search path in case someone drops the schema?

    Is an invalid search path really that critical (read security
    issue)?


Jan

--

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck@Yahoo.com #