From: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
---|---|
To: | khera(at)yertle(dot)int(dot)kciLink(dot)com |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: pgpool simple feature request |
Date: | 2005-02-09 06:31:56 |
Message-ID: | 20050209.153156.51836943.t-ishii@sra.co.jp |
Views: | Raw Message | Whole Thread | 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?
Yes. pgpool issues "RESET ALL" at the end of each client
connection. See "reset_query_list" directive.
--
Tatsuo Ishii
From | Date | Subject | |
---|---|---|---|
Next Message | John DeSoi | 2005-02-09 06:35:51 | Re: Postgresql and Macintosh |
Previous Message | John DeSoi | 2005-02-09 06:30:25 | Re: Database permissions |