Re: INSERT ... ON CONFLICT UPDATE and logical decoding
От | Andres Freund |
---|---|
Тема | Re: INSERT ... ON CONFLICT UPDATE and logical decoding |
Дата | |
Msg-id | 20150220235216.GI12653@awork2.anarazel.de обсуждение исходный текст |
Ответ на | Re: INSERT ... ON CONFLICT UPDATE and logical decoding (Peter Geoghegan <pg@heroku.com>) |
Ответы |
Re: INSERT ... ON CONFLICT UPDATE and logical decoding
|
Список | pgsql-hackers |
On 2015-02-20 15:44:12 -0800, Peter Geoghegan wrote: > On Thu, Feb 19, 2015 at 2:11 AM, Andres Freund <andres@2ndquadrant.com> wrote: > > Yes. It'd be easiest if the only the final insert/update were actually > > WAL logged as full actions. > > Well, that implies that we'd actually know that we'd succeed when WAL > logging the speculative heap tuple's insertion. I don't think it does. It'd certainly be possible to simply only emit the final WAL logging action once the insertion has actually non-speculatively succeeded. We might decide against that for eefficiency or complexity reasons, but it'd be far from impossible or even ugly. We could even not log the actual values for the speculative insertion - after all, those aren't needed if we crash halfway through... Greetings, Andres Freund -- Andres Freund http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services
В списке pgsql-hackers по дате отправления: