Re: logical changeset generation v6

From: Steve Singer <steve(at)ssinger(dot)info>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Peter Geoghegan <pg(at)heroku(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: logical changeset generation v6
Date: 2013-09-24 15:51:02
Message-ID: BLU0-SMTP640152826F1EC4637A552BDC2E0@phx.gbl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 09/24/2013 11:21 AM, Andres Freund wrote:
> Not having a consumer of the walsender interface included sounds like a
> bad idea to me, even if it were only useful for testing. Now, you could
> argue it should be in /contrib - and I wouldn't argue against that
> except it shares code with the rest of src/bin/pg_basebackup.

+1 on pg_receivellog (or whatever better name we pick) being somewhere.
I found the pg_receivellog code very useful as an example and for
debugging/development purposes.
It isn't something that I see useful for the average user and I think
the use-cases it meets are closer to other things we usually put in /contrib

Steve

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2013-09-24 15:57:21 Re: Improving avg performance for numeric
Previous Message Stas Kelvich 2013-09-24 15:44:22 Cube extension types support