Horton

Re: timeout implementation issues

Hiroshi Inoue <inoue@tpf.co.jp>

View thread
From: "Hiroshi Inoue" <Inoue@tpf.co.jp>
To: "Peter Eisentraut" <peter_e@gmx.net>, "Tom Lane" <tgl@sss.pgh.pa.us>
Cc: "Bruce Momjian" <pgman@candle.pha.pa.us>, "Jessica Perry Hekman" <jphekman@dynamicdiagrams.com>, "Jan Wieck" <janwieck@yahoo.com>, "Barry Lind" <barry@xythos.com>, <pgsql-hackers@postgresql.org>
Date: 2002-04-07T07:59:16Z
Lists: pgsql-hackers 
> -----Original Message-----
> From: Peter Eisentraut [mailto:peter_e@gmx.net]
> 
> 
> I guess it's a matter of definition: Do you consider SET variables
> database state or session metadata?  

Session metadata IMHO. If there are(would be) database state
variables we should introduce another command for them.
For example I don't think QUERY_TIMEOUT is such a variable.
As I mentioned many times we can set QUERY_TIMEOUT before
each query. If the overhead is an issue we can keep track of the
varaible and reduce the command calls to minimum easily. 

regards,
Hiroshi Inoue