> 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 -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
