Horton

Re: timeout implementation issues

Tom Lane <tgl@sss.pgh.pa.us>

View thread
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Karel Zak <zakkr@zf.jcu.cz>
Cc: Bruce Momjian <pgman@candle.pha.pa.us>, Peter Eisentraut <peter_e@gmx.net>, Thomas Lockhart <lockhart@fourpalms.org>, Jessica Perry Hekman <jphekman@dynamicdiagrams.com>, Hiroshi Inoue <Inoue@tpf.co.jp>, Jan Wieck <janwieck@yahoo.com>, Barry Lind <barry@xythos.com>, pgsql-hackers@postgresql.org
Date: 2002-04-09T13:20:22Z
Lists: pgsql-hackers 
Karel Zak <zakkr@zf.jcu.cz> writes:
>  It's good point. Why not make it more transparent? You want
>  encapsulate it to standard and current SET statement, but if it's
>  something different why not use for it different statement?

>     SET SESSION search_path TO 'something';

But a plain SET is also setting the value for the session.  What's
the difference?  Why should a user remember that he must use this
syntax for search_path, and not for any other variables (or perhaps
only one or two other ones, further down the road)?

			regards, tom lane