Re: pgsql: Fix document bug regarding read only transactions.

From: Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp>
To: tgl(at)sss(dot)pgh(dot)pa(dot)us
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Fix document bug regarding read only transactions.
Date: 2017-06-15 22:54:51
Message-ID: 20170616.075451.424455466898366794.t-ishii@sraoss.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Noah Misch 2017-06-16 07:19:19 pgsql: Reconcile nodes/*funcs.c with PostgreSQL 10 work.
Previous Message Tom Lane 2017-06-15 19:56:17 pgsql: Make configure check for IPC::Run when --enable-tap-tests is spe