From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql: Remove the last vestige of server-side autocommit. |
Date: | 2014-11-06 00:35:30 |
Message-ID: | E1XmB2w-0008Ho-NO@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Remove the last vestige of server-side autocommit.
Long ago we briefly had an "autocommit" GUC that turned server-side
autocommit on and off. That behavior was removed in 7.4 after concluding
that it broke far too much client-side logic, and making clients cope with
both behaviors was impractical. But the GUC variable was left behind, so
as not to break any client code that might be trying to read its value.
Enough time has now passed that we should remove the GUC completely.
Whatever vestigial backwards-compatibility benefit it had is outweighed by
the risk of confusion for newbies who assume it ought to do something,
as per a recent complaint from Wolfgang Wilhelm.
In passing, adjust what seemed to me a rather confusing documentation
reference to libpq's autocommit behavior. libpq as such knows nothing
about autocommit, so psql is probably what was meant.
Branch
------
master
Details
-------
http://git.postgresql.org/pg/commitdiff/525a489915cad1c5b2fc39e43e8005025afe63b2
Modified Files
--------------
doc/src/sgml/ecpg.sgml | 2 +-
src/backend/utils/misc/check_guc | 2 +-
src/backend/utils/misc/guc.c | 25 -------------------------
3 files changed, 2 insertions(+), 27 deletions(-)
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2014-11-06 07:33:12 | pgsql: C comment: mention why the Gregorian calendar is used pre-1582 |
Previous Message | Robert Haas | 2014-11-05 23:22:56 | pgsql: Fix thinko in commit 2bd9e412f92bc6a68f3e8bcb18e04955cc35001d. |