Re: timeout implementation issues

From: Thomas Swan <tswan(at)olemiss(dot)edu>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Jessica Perry Hekman <jphekman(at)dynamicdiagrams(dot)com>, Jan Wieck <janwieck(at)yahoo(dot)com>, Barry Lind <barry(at)xythos(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: timeout implementation issues
Date: 2002-04-08 04:09:07
Message-ID: 3CB117E3.5050802@olemiss.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title></title>
</head>
<body>
Bruce Momjian wrote:<br>
<blockquote type="cite"
cite="mid200204080317(dot)g383Hj511314(at)candle(dot)pha(dot)pa(dot)us">
<pre wrap="">Hiroshi Inoue wrote:<br></pre>
<blockquote type="cite">
<pre wrap="">Bruce Momjian wrote:<br></pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">I guess it's a matter of definition: Do you consider SET variables<br>database state or session metadata? I think some are this and some are<br>that. I'm not sure how to draw the line, but throwing everything from one<br>category into the other isn't my favorite solution.<br></pre>
</blockquote>
<pre wrap="">You seem to be suggesting that we should make a variable-by-variable<br>decision about whether SET variables roll back on ABORT or not. I think<br>that way madness lies; we could spend forever debating which vars are<br>which, and then who will remember without consulting the documentation?<br><br>I feel we should just do it. Yeah, there might be some corner cases<br>where it's not the ideal behavior; but you haven't convinced me that<br>there are more cases where it's bad than where it's good. You sure<br>haven't convinced me that it's worth making SET's behavior<br>nigh-unpredictable-without-a-manual, which is what per-variable behavior<br>would be.<br></pre>
</blockquote>
<pre wrap="">I am with Tom on this one. (Nice to see he is now arguing on my side.)<br></pre>
</blockquote>
<pre wrap="">I vote against you. If a variable is local to the session, you<br>can change it as you like without bothering any other user(session).<br>Automatic resetting of the varibales is rather confusing to me.<br></pre>
</blockquote>
<pre wrap=""><!----><br>I don't see how this relates to other users. All SET commands that can<br>be changed in psql are per backend, as far as I remember.</pre>
</blockquote>
Per backend or per session?<br>
<blockquote type="cite"
cite="mid200204080317(dot)g383Hj511314(at)candle(dot)pha(dot)pa(dot)us">
<pre wrap=""><br><br></pre>
</blockquote>
<br>
<br>
</body>
</html>

Attachment Content-Type Size
unknown_filename text/html 2.1 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2002-04-08 04:40:56 Re: unknownin/out patch (was [HACKERS] PQescapeBytea is not multibyte aware)
Previous Message Tatsuo Ishii 2002-04-08 03:52:02 Re: PQescapeBytea is not multibyte aware