transaction_isolation vs. default_transaction_isolation

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org>
Subject: transaction_isolation vs. default_transaction_isolation
Date: 2009-10-13 05:13:33
Message-ID: 4AD40C7D.3000503@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Davis 2009-10-13 05:22:30 Re: transaction_isolation vs. default_transaction_isolation
Previous Message Itagaki Takahiro 2009-10-13 02:39:49 Skip WAL in ALTER TABLE