Re: A bad behavior under autocommit off mode

From: Greg Stark <gsstark(at)mit(dot)edu>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: A bad behavior under autocommit off mode
Date: 2003-03-26 18:51:42
Message-ID: 87k7emklkx.fsf@stark.dyndns.tv
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:

> How about sending an INFO or special taged message to the client when
> there is a GUC change, and have report_changes as a GUC variable that
> controls it?

just brainstorming. But if you're changing the on-wire representation, perhaps
every transaction should just have a autocommit flag carried with it. Then you
don't need any persistent setting, and the library doesn't need to be editing
the text of transactions to insert BEGIN/COMMITs, the library just needs to
either set the flag or not on every transaction.

--
greg

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2003-03-26 22:06:32 Re: The old "heap_mark4update" error
Previous Message Larry Rosenman 2003-03-26 18:01:30 Re: to_char(interval) --- done?