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

From Tom Lane
Subject Re: [COMMITTERS] pgsql: Fix document bug regarding read only transactions.
Date
Msg-id 31121.1497535980@sss.pgh.pa.us
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: Fix document bug regarding read onlytransactions.  (Tatsuo Ishii <ishii@sraoss.co.jp>)
Responses Re: [COMMITTERS] pgsql: Fix document bug regarding read onlytransactions.  (Tatsuo Ishii <ishii@sraoss.co.jp>)
List pgsql-committers
Tatsuo Ishii <ishii@sraoss.co.jp> writes:
>> Right, but what I think it is comparing is a read-only transaction
>> on the master and a transaction on the standby.  The former can do
>> nextval() on temp sequences, the latter can't.

> But we cannot create temp sequences on stanbys in the first place.
> Still do you think there's value to refer to nextval() on temp
> sequences here?

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.

            regards, tom lane


pgsql-committers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [COMMITTERS] pgsql: Fix problems related to RangeTblEntry membersenrname and enrtup
Next
From: Tom Lane
Date:
Subject: Re: [COMMITTERS] pgsql: Fix problems related to RangeTblEntry members enrname and enrtup