| From: | Vivek Khera <khera(at)yertle(dot)int(dot)kciLink(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: pgpool simple feature request |
| Date: | 2005-02-08 20:49:42 |
| Message-ID: | x7mzuevkt5.fsf@yertle.int.kciLink.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
>>>>> "TI" == Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> writes:
TI> Yes, I thought about that too. Probably we need two kinds of
TI> initializations:
TI> 1) initilization for each new connection (as you requested)
TI> 2) initilization for each new client connection
I think this latter one is important. Take the case where I do some
"set FOO BAR" values to alter the query (eg, statement timeout or
sequence scan disable) which should be reset on new client connection
when it re-uses a backend connection.
Or is this magically handled already?
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Vivek Khera, Ph.D. Khera Communications, Inc.
Internet: khera(at)kciLink(dot)com Rockville, MD +1-301-869-4449 x806
AIM: vivekkhera Y!: vivek_khera http://www.khera.org/~vivek/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruno Wolff III | 2005-02-08 20:52:43 | Removing duplicates |
| Previous Message | awitney | 2005-02-08 19:40:06 | hi |