On Thu, Aug 12, 2010 at 9:43 PM, Fujii Masao masao.fu...@gmail.com wrote:
On Fri, Aug 13, 2010 at 10:24 AM, Robert Haas robertmh...@gmail.com wrote:
On Thu, Aug 12, 2010 at 12:11 AM, Fujii Masao masao.fu...@gmail.com wrote:
It appears to me that RecordTransactionCommit() only needs to WAL-log
On Thu, Aug 12, 2010 at 12:11 AM, Fujii Masao masao.fu...@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
On Fri, Aug 13, 2010 at 10:24 AM, Robert Haas robertmh...@gmail.com wrote:
On Thu, Aug 12, 2010 at 12:11 AM, Fujii Masao masao.fu...@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
On Wed, Aug 11, 2010 at 1:17 AM, Fujii Masao masao.fu...@gmail.com wrote:
On Tue, Aug 10, 2010 at 9:30 AM, Robert Haas robertmh...@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
On 11/08/10 16:46, Robert Haas wrote:
On Wed, Aug 11, 2010 at 1:17 AM, Fujii Masaomasao.fu...@gmail.com wrote:
On Tue, Aug 10, 2010 at 9:30 AM, Robert Haasrobertmh...@gmail.com wrote:
It appears to me that RecordTransactionCommit() only needs to WAL-log
shared invalidation messages when
On Wed, Aug 11, 2010 at 11:35 PM, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com wrote:
On 11/08/10 16:46, Robert Haas wrote:
On Wed, Aug 11, 2010 at 1:17 AM, Fujii Masaomasao.fu...@gmail.com
wrote:
On Tue, Aug 10, 2010 at 9:30 AM, Robert Haasrobertmh...@gmail.com
wrote:
It
On Tue, Aug 10, 2010 at 9:30 AM, Robert Haas robertmh...@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.
Perhaps right. During
