Re: Replication identifiers, take 4

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Andres Freund <andres(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Steve Singer <steve(at)ssinger(dot)info>, Petr Jelinek <petr(at)2ndquadrant(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
Subject: Re: Replication identifiers, take 4
Date: 2015-02-22 15:03:59
Message-ID: 54E9EFDF.1060105@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2/15/15 7:24 PM, Andres Freund wrote:
> On 2015-02-16 01:21:55 +0100, Andres Freund wrote:
>> Here's my next attept attempt at producing something we can agree
>> upon.
>>
>> The major change that might achieve that is that I've now provided a
>> separate method to store the origin_id of a node. I've made it
>> conditional on !REPLICATION_IDENTIFIER_REUSE_PADDING, to show both
>> paths. That new method uses Heikki's xlog rework to dynamically add the
>> origin to the record if a origin is set up. That works surprisingly
>> simply.

I'm trying to figure out what this feature is supposed to do, but the
patch contains no documentation or a commit message. Where is one
supposed to start?

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2015-02-22 15:11:30 Re: hash agg is slower on wide tables?
Previous Message Peter Eisentraut 2015-02-22 15:00:28 Re: Enforce creation of destination folders for source files in pg_regress (Was: pg_regress writes into source tree)