Tatsuo Ishii wrote: >> Fujii Masao wrote: >>> On Mon, Feb 1, 2010 at 7:40 PM, Heikki Linnakangas >>> <heikki.linnakan...@enterprisedb.com> wrote: >>>> So you get those messages when the table is *not* a temporary table. I >>>> can see now what Fujii was trying to say. His patch seems Ok, though >>>> perhaps it would be better to move the responsibility of calling >>>> XLogReportUnloggedStatement() to the callers of heap_sync(). When I put >>>> it in heap_sync(), I didn't take into account that it's sometimes called >>>> just to flush buffers from buffer cache, not to fsync() non-WAL-logged >>>> operations. >>> As you said, I moved the responsibility of calling >>> XLogReportUnloggedStatement() >>> to the callers of heap_sync(). Here is the patch. >> Committed. The use_wal parameter to end_heap_rewrite() was not >> necessary, that information is already in RewriteState, so I took that out. > > Are we going to bump up frontend/backend protocol version 3.0 to 3.x > or some such?
No, this doesn't affect the normal FE/BE protocol. The message header was added to the streaming replication messages that are sent within CopyData messages. -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
