Postgres Pro
Downloads
Home   >   mailing lists

Re: [HACKERS] read-only database - Mailing list pgsql-patches

From Satoshi Nagayasu
Subject Re: [HACKERS] read-only database
Date
Msg-id 427EDD72.5080806@nttdata.co.jp
Whole thread Raw
In response to Re: [HACKERS] read-only database  (Alvaro Herrera <alvherre@dcc.uchile.cl>)
Responses Re: [HACKERS] read-only database  (Satoshi Nagayasu <nagayasus@nttdata.co.jp>)
List pgsql-patches
Tree view 
> But the second is only a subset of the first, no?  So why not just
> implement the first?  Put another way, why do you think the second is
> necessary?

Because there is "default_transaction_read_only" option and
implementation.

My implementation is an extension of the existing option.

I wanted to make the postmaster read-only, and found
"default_transaction_read_only" option, but it can be overwritten.

--
NAGAYASU Satoshi <nagayasus@nttdata.co.jp>
OpenSource Development Center,
NTT DATA Corp. http://www.nttdata.co.jp/

pgsql-patches by date:

Previous
From: Tom Lane
Date:
Subject: Re: Added columns to pg_stat_activity
Next
From: Satoshi Nagayasu
Date:
Subject: Re: [HACKERS] read-only database