Thread: set in transaction

I have a query that performs much better using
set enable_seqscan = false; The problem is that variables sets don't get rolled back when
a transaction aborts, so I'm forced to destroy my db connection rather than putting it
back in the pool. Is there any way around this in general other than just setting
enable_seqscan = true; and the end?

On Tue, Dec 03, 2002 at 20:01:56 -0500,
  Joseph Shraibman <jks@selectacast.net> wrote:
> I have a query that performs much better using
> set enable_seqscan = false; The problem is that variables sets don't get
> rolled back when a transaction aborts, so I'm forced to destroy my db
> connection rather than putting it back in the pool. Is there any way around
> this in general other than just setting enable_seqscan = true; and the end?

They do in 7.3.