Re: [COMMITTERS] pgsql: Fix document bug regarding read onlytransactions. - Mailing list pgsql-committers

From Tatsuo Ishii
Subject Re: [COMMITTERS] pgsql: Fix document bug regarding read onlytransactions.
Date
Msg-id 20170616.075451.424455466898366794.t-ishii@sraoss.co.jp
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: Fix document bug regarding read only transactions.  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-committers
> You're right that the statement is irrelevant in the context of what
> a standby can or can't do, but what I'm worried about is that someone
> will read it and believe that it represents the whole truth about
> what read-only master transactions can do.  The previous wording was
> also irrelevant to the context of a standby, and yet this whole thread
> exists because somebody complained that it's an inaccurate description
> of the restrictions on such a master transaction.  Well, it's still
> inaccurate.

Then I think we should add more commands including ANALYZE, VACUUM and
strong LOCKS here. There's no specific reason to pick up only
nextval(), LISTEN and NOTIFY.

Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: [COMMITTERS] pgsql: Make configure check for IPC::Run when --enable-tap-tests isspe
Next
From: Noah Misch
Date:
Subject: [COMMITTERS] pgsql: Reconcile nodes/*funcs.c with PostgreSQL 10 work.