Re: A bad behavior under autocommit off mode - Mailing list pgsql-hackers

From Greg Stark
Subject Re: A bad behavior under autocommit off mode
Date
Msg-id 87k7emklkx.fsf@stark.dyndns.tv
Whole thread Raw
In response to Re: A bad behavior under autocommit off mode  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
Bruce Momjian <pgman@candle.pha.pa.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



pgsql-hackers by date:

Previous
From: Larry Rosenman
Date:
Subject: Re: to_char(interval) --- done?
Next
From: Tom Lane
Date:
Subject: Re: The old "heap_mark4update" error