On Thu, Aug 12, 2010 at 9:43 PM, Fujii Masao wrote:
> On Fri, Aug 13, 2010 at 10:24 AM, Robert Haas wrote:
>> On Thu, Aug 12, 2010 at 12:11 AM, Fujii Masao wrote:
>>> It appears to me that RecordTransactionCommit() only needs to WAL-log
>>> shared invalidation messages when wal_level is
On Fri, Aug 13, 2010 at 10:24 AM, Robert Haas wrote:
> On Thu, Aug 12, 2010 at 12:11 AM, Fujii Masao 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
On Thu, Aug 12, 2010 at 12:11 AM, Fujii Masao 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
On Wed, Aug 11, 2010 at 11:35 PM, Heikki Linnakangas
wrote:
> On 11/08/10 16:46, Robert Haas wrote:
>>
>> On Wed, Aug 11, 2010 at 1:17 AM, Fujii Masao
>> wrote:
>>>
>>> On Tue, Aug 10, 2010 at 9:30 AM, Robert Haas
>>> wrote:
It appears to me that RecordTransactionCommit() only needs to
On 11/08/10 16:46, Robert Haas wrote:
On Wed, Aug 11, 2010 at 1:17 AM, Fujii Masao wrote:
On Tue, Aug 10, 2010 at 9:30 AM, Robert Haas 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 gua
On Wed, Aug 11, 2010 at 1:17 AM, Fujii Masao wrote:
> On Tue, Aug 10, 2010 at 9:30 AM, Robert Haas 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
On Tue, Aug 10, 2010 at 9:30 AM, Robert Haas 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, ther
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. Am I
missing something?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Post
