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 02:00:32
Message-ID: 20170615.110032.244878105781471727.t-ishii@sraoss.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

> 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?

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

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tatsuo Ishii 2017-06-15 02:28:52 pgsql: Fix typo in PostgreSQL 10.0 release note.
Previous Message Tom Lane 2017-06-15 01:44:15 Re: pgsql: Fix document bug regarding read only transactions.