Re: RecordTransactionCommit() and SharedInvalidationMessages

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: RecordTransactionCommit() and SharedInvalidationMessages
Date: 2010-08-11 05:17:10
Message-ID: AANLkTind-5tstrf0oLtr0FcQ01YvdRyWEBANNxxyZfdC@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Aug 10, 2010 at 9:30 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> It appears to me that RecordTransactionCommit() only needs to WAL-log
> shared invalidation messages when wal_level is hot_standby, but I
> don't see a guard to prevent it from doing it in all cases.

Perhaps right. During not hot standby, there is no backend which the
startup process should send invalidation message to in the standby.
So, ISTM we don't need to log invalidation message when wal_level is
not hot_standby.

Regards,

--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2010-08-11 05:31:42 assertions and constraint triggers
Previous Message Greg Smith 2010-08-11 04:51:36 Re: Cost of AtEOXact_Buffers in --enable-cassert