Re: [PATCH] Logical decoding support for sequence advances
| От | Craig Ringer |
|---|---|
| Тема | Re: [PATCH] Logical decoding support for sequence advances |
| Дата | |
| Msg-id | CAMsr+YFv5oFnk=1qkSoCeSGPRiO742Lh8CWB4DPsdA3nSth-=A@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: [PATCH] Logical decoding support for sequence advances (Petr Jelinek <petr@2ndquadrant.com>) |
| Ответы |
Re: [PATCH] Logical decoding support for sequence advances
|
| Список | pgsql-hackers |
On 1 March 2016 at 05:30, Petr Jelinek <petr@2ndquadrant.com> wrote:
On 29/02/16 03:23, Craig Ringer wrote:
Sound reasonable?
I wonder if it would be acceptable to create new info flag for RM_SEQ_ID that would behave just like XLOG_SEQ_LOG but would be used only for the nontransactional updates (nextval) so that decoding could easily differentiate between transactional and non-transactional update of sequence and then just either call the callback immediately or add the change to reorder buffer based on that. The redo code could just have simple OR expression to behave same with both of the info flags.
That's much cleaner than trying to keep track of sequence creations and really pretty harmless. I'll give that a go and see how it looks.
Seems like simpler solution than building all the tracking code on the decoding side to me.
+1
В списке pgsql-hackers по дате отправления: