Re: Cmpact commits and changeset extraction - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Cmpact commits and changeset extraction
Date
Msg-id CA+TgmoabZVhFWZDk7w1sinLKu8YvrwJpcY=nid2ZkygC2mPhoQ@mail.gmail.com
Whole thread Raw
In response to Re: Cmpact commits and changeset extraction  (Andres Freund <andres@2ndquadrant.com>)
Responses Re: Cmpact commits and changeset extraction
List pgsql-hackers
On Mon, Sep 30, 2013 at 5:34 PM, Andres Freund <andres@2ndquadrant.com> wrote:
>> What's wrong with #1?
>
> It seems confusing that a changeset stream in database #1 will contain
> commits (without corresponding changes) from database #2. Seems like aaa
> pola violation to me.

I don't really see the problem.  A transaction could be empty for lots
of reasons; it may have obtained an XID without writing any data, or
whatever it's changed may be outside the bounds of logical rep.  Maybe
you should just skip replay of transactions with no useful content.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Minmax indexes
Next
From: Andres Freund
Date:
Subject: Re: [PERFORM] Cpu usage 100% on slave. s_lock problem.