On 2013-10-08 15:02:39 -0400, Steve Singer wrote: > On 10/07/2013 09:32 AM, Andres Freund wrote: > >Todo: > >* rename treat_as_catalog_table, after agreeing on the new name > >* rename remaining timetravel function names > >* restrict SuspendDecodingSnapshots usage to RelationInitPhysicalAddr, > > that ought to be enough. > >* add InLogicalDecoding() function. > >* throw away older data when reading xl_running_xacts records, to deal > > with immediate shutdowns/crashes > > What is your current plan for decoding sequence updates? Is this something > that you were going to hold-off on supporting till a future version? ( know > this was discussed a while ago but I don't remember where it stands now)
I don't plan to implement it as part of this - the optimizations in sequences make it really unsuitable for that (nontransaction, allocated in bulk, ...). Simon had previously posted about "sequence AMs", and I have a prototype patch that implements that concept (which needs considerable cleanup). I plan to post about it whenever this is finished. I think many replication solutions that care about sequences in a nontrivial will want to implement their own sequence logic anyway, so I think that's not a bad path. 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
