"Marcus Andree S. Magalhaes" <marcus(dot)magalhaes(at)vlinfo(dot)com(dot)br> writes:
> But, since we're using pooled connections, we must be extra
> careful and ensure all connections have the enable_seqscan
> reset to its default.
If you are concerned about failing to reset parameters, use "SET LOCAL
foo" instead of plain "SET foo" (and of course, do this inside a
transaction block). With the LOCAL option the parameter is guaranteed
to be reset at transaction end.
> Do the pooling system resets the "enable_seqscan" variable
> when the connections are delivered to the clients or we
> *must* do it ourselves?
I think it is reasonable to expect a pooling system to deliver you a
fresh transaction. It is not reasonable to expect it to go and issue
explicit SET commands to undo things you've done.
regards, tom lane
In response to
pgsql-jdbc by date
|Next:||From: Kris Jurka||Date: 2004-04-02 06:55:04|
|Subject: Re: patch: enforce the requirements for scrollable resultsets|
|Previous:||From: Sanjay Singh||Date: 2004-04-02 03:42:59|