| From: | Jan Wieck <janwieck(at)yahoo(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL HACKERS <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: timeout implementation issues |
| Date: | 2002-04-08 14:46:11 |
| Message-ID: | 200204081446.g38EkBL12342@saturn.janwieck.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Karel Zak <zakkr(at)zf(dot)jcu(dot)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(at)Yahoo(dot)com #
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-04-08 15:08:31 | Re: timeout implementation issues |
| Previous Message | Jan Wieck | 2002-04-08 14:15:18 | Re: timeout implementation issues |