On 2014-01-16 11:01:29 -0800, Jeff Janes wrote: > I think the argument is that drawing the next value from a sequence can > generate xlog that needs to be flushed, but doesn't assign an xid.
Then that should assign an xid. Which would yield correct behaviour with async commit where it's currently *not* causing a WAL flush at all unless a page boundary is crossed. I've tried arguing that way before... Greetings, Andres Freund -- Andres Freund http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
