Re: [HACKERS] read-only database

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Satoshi Nagayasu <nagayasus(at)nttdata(dot)co(dot)jp>, pgsql-patches(at)postgresql(dot)org
Subject: Re: [HACKERS] read-only database
Date: 2005-05-06 23:35:31
Message-ID: 27236.1115422531@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> It seems server_read_only is the same as default_transaction_read_only
> except it can't be changed.

I thought the TODO item was for a low-level read-only option, suitable
for trying to look at a corrupted database or run off a read-only volume.
This is very far from being that --- it allows temp table creation/use,
and it still eats transaction IDs so it is certainly not read-only to
xlog or clog.

I am not sure I see any use case for this implementation: it is
read-only enough to get in your way, without being read-only enough
to derive any real benefit.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Markus Bertheau 2005-05-07 00:00:20 Re: CVS HEAD problem: psql: symbol lookup error:
Previous Message Bruce Momjian 2005-05-06 23:09:18 Re: [HACKERS] read-only database

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2005-05-07 02:10:12 Re: [HACKERS] read-only database
Previous Message Bruce Momjian 2005-05-06 23:09:18 Re: [HACKERS] read-only database