[prev in list] [next in list] [prev in thread] [next in thread] 

List:       postgresql-general
Subject:    Re: [HACKERS] [PATCH] Logical decoding support for sequence advances
From:       Alvaro Herrera <alvherre () 2ndquadrant ! com>
Date:       2016-02-29 22:38:03
Message-ID: 20160229223803.GA339424 () alvherre ! pgsql
[Download RAW message or body]

Petr Jelinek wrote:

> 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.
> 
> Seems like simpler solution than building all the tracking code on the
> decoding side to me.

Given the mess in Craig's description, the new info flag sounds a much
more reasonable approach to me.

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, 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
[prev in list] [next in list] [prev in thread] [next in thread]