transaction_isolation vs. default_transaction_isolation - Mailing list pgsql-hackers

From Josh Berkus
Subject transaction_isolation vs. default_transaction_isolation
Date
Msg-id 4AD40C7D.3000503@agliodbs.com
Whole thread Raw
Responses Re: transaction_isolation vs. default_transaction_isolation  (Itagaki Takahiro <itagaki.takahiro@oss.ntt.co.jp>)
Re: transaction_isolation vs. default_transaction_isolation  (Jeff Davis <pgsql@j-davis.com>)
List pgsql-hackers
Hackers,

A slew of settings in postgresql.conf, including work_mem, search_path,
DateStyle, and about 80 others are effectively just defaults for new
connections, since they can be changed by any user.

However, for *two* settings, and two settings only, we distinguish that
by naming an identical setting "default_*" in postgresql.conf.  This is
confusing and inconsistent with the rest of the GUCS.  Namely:

default_transaction_isolation
default_transaction_read_only
transaction_isolation
transaction_read_only

For 8.5, I would like to consolidate these into only 2 settings and drop
the default_* settings.

--Josh Berkus


pgsql-hackers by date:

Previous
From: Itagaki Takahiro
Date:
Subject: Skip WAL in ALTER TABLE
Next
From: Itagaki Takahiro
Date:
Subject: Re: transaction_isolation vs. default_transaction_isolation