Re: Changeset Extraction v7.3

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Thom Brown <thom(at)linux(dot)com>
Cc: Andres Freund <andres(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Changeset Extraction v7.3
Date: 2014-01-28 16:53:41
Message-ID: CA+TgmoZqA++6fpEJy9SCFnOEUSJMF1StyNFBoe3Uq+UJ5U1HHg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jan 28, 2014 at 11:49 AM, Thom Brown <thom(at)linux(dot)com> wrote:
> On 27 January 2014 16:20, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
>> Hi,
>>
>> Here's the next version of the patchset. The following changes have been
>> made:
>> * move xmin pegging and more logic responsibility to procarray.c
>> * split all support for changeset extraction from the initial slot patch
>> * always register an before_shmem_exit handler when
>> max_replication_slots is registered, not just while a slot is acquired
>> * move some patch hunks to earlier patches, especially the
>> ReplicationSlotAcquire() call for physical rep that accidentally
>> slipped and the SQL accessible slot manipulation functions
>> * minor stuff
>
> 0001 doesn't apply cleanly due to commit
> ea9df812d8502fff74e7bc37d61bdc7d66d77a7f.
>
> The rest are fine.

I've rebased it here and am hacking on it still.

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2014-01-28 17:01:17 Re: Performance Improvement by reducing WAL for Update Operation
Previous Message Jeff Janes 2014-01-28 16:53:37 Re: A better way than tweaking NTUP_PER_BUCKET