Re: RecordTransactionCommit() and SharedInvalidationMessages - Mailing list pgsql-hackers

From Robert Haas
Subject Re: RecordTransactionCommit() and SharedInvalidationMessages
Date
Msg-id AANLkTin5uRUvAOgeMxn1EyPiYg-FJ5SAkkn5wNuReA21@mail.gmail.com
Whole thread Raw
In response to Re: RecordTransactionCommit() and SharedInvalidationMessages  (Fujii Masao <masao.fujii@gmail.com>)
Responses Re: RecordTransactionCommit() and SharedInvalidationMessages  (Fujii Masao <masao.fujii@gmail.com>)
List pgsql-hackers
On Thu, Aug 12, 2010 at 12:11 AM, Fujii Masao <masao.fujii@gmail.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.
[...]
>>> The fix looks pretty simple (see attached), although I don't have any
>>> clear idea how to test it.
>> Should use XLogStandbyInfoActive() macro, for the sake of consistency.
> And, RelcacheInitFileInval should be initialized with false just in case.

How about this?

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company

Attachment

pgsql-hackers by date:

Previous
From: Greg Smith
Date:
Subject: Re: Patch to show individual statement latencies in pgbench output
Next
From: Robert Haas
Date:
Subject: Re: including backend ID in relpath of temp rels - updated patch