Re: transaction_isolation vs. default_transaction_isolation

From: Itagaki Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: transaction_isolation vs. default_transaction_isolation
Date: 2009-10-13 05:28:44
Message-ID: 20091013142039.A6FE.52131E4D@oss.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Josh Berkus <josh(at)agliodbs(dot)com> wrote:

> default_transaction_isolation
> default_transaction_read_only

They are settings of transaction_isolation and transaction_read_only
for *next* transactions, no?

> transaction_isolation
> transaction_read_only

Non-default versions are almost read-only variables
because we can set them at the beginning of transactions.

BEGIN;
SET transaction_isolation = 'serializable';
SET default_transaction_isolation = 'read committed';
SHOW transaction_isolation;
=> serializable
SHOW default_transaction_isolation;
=> read committed
COMMIT;
-- next transaction uses default_transaction_isolation
SHOW transaction_isolation;
=> read committed

Regards,
---
ITAGAKI Takahiro
NTT Open Source Software Center

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2009-10-13 05:38:00 Re: transaction_isolation vs. default_transaction_isolation
Previous Message Jeff Davis 2009-10-13 05:22:30 Re: transaction_isolation vs. default_transaction_isolation