From: Andres Freund <andres@2ndquadrant.com>
To: pgsql-hackers@postgresql.org
Subject: Re: Changeset Extraction v7.8
Date: Thu, 27 Feb 2014 17:56:08 +0100
Message-ID: <20140227165608.GJ28858@alap3.anarazel.de> (raw)
In-Reply-To: <20140115002223.GA17204@awork2.anarazel.de>
References: <20140115002223.GA17204@awork2.anarazel.de>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
Hi,
Attached you can find version 7.8 of this patcheset. Changes since 7.7
include:
* Signature changes of the SQL changeset SRFs to support limits based on
LSN and/or number of returned rows (pg_logical_slot_get_changes() et
al) and to make parameter passing optional (by adding a DEFAULT '{}'
to the variadic argument)
* heap_page_prune_opt() now decides itself which horizon to use,
removing a good amount of duplicated logic
* GetOldestXmin() now has a Relation parameter that can be NULL instead
of the former allDbs (existing in master) and systable (just this
branch) parameters, also removing code duplication.
* pg_create_logical_replication_slot() is now defined in slotfuncs.c
* a fair number of cosmetic and comment changes
The open issues that I know of are:
* do we modify struct SnapshotData to be polymorphic based on some tag
or move comments there?
* How/whether to change the exclusive lock on the ProcArrayLock in
CreateInitDecodingContext()
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: andres@2ndquadrant.com
Subject: Re: Changeset Extraction v7.8
In-Reply-To: <20140227165608.GJ28858@alap3.anarazel.de>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox