On 05/05/17 02:00, Andres Freund wrote: > Hi, > > On 2017-05-02 08:55:53 +0200, Petr Jelinek wrote: >> Aah, now I understand we talked about slightly different things, I >> considered the running thing to be first step towards tracking aborted >> txes everywhere. >> I think >> we'll have to revisit tracking of aborted transactions in PG11 then >> though because of the 'snapshot too large' issue when exporting, at >> least I don't see any other way to fix that. > > FWIW, that seems unnecessary - we can just check for that using the > clog. Should be very simple to check for aborted xacts when exporting > the snapshot (like 2 lines + comments). That should address your > concern, right?
Right, because there isn't practical difference between running and aborted transaction for us so we don't mind if the abort has happened in the future. Yeah the export code could do the check seems quite simple. -- Petr Jelinek 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
