From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_basebackup and replication slots |
Date: | 2015-07-01 14:35:26 |
Message-ID: | 5593FAAE.5020706@gmx.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 7/1/15 8:37 AM, Michael Paquier wrote:
> On Wed, Jul 1, 2015 at 10:33 AM, Peter Eisentraut wrote:
>> (If you're looking at the patch and wondering why there is no code to
>> actually do anything with the replication slot, that's because the code
>> that does the WAL streaming is already aware of replication slots
>> because of the pg_receivexlog functionality that it also serves. So all
>> that needs to be done is set replication_slot.)
>
> This is cool to see this patch taking shape.
>
> + my ($stdout, $stderr);
> + run [ 'psql', '-X', '-A', '-t', '-q', '-d', $dbname, '-f', '-' ],
> '<', \$sql, '>', \$stdout, '2>', \$stderr or die;
> + chomp $stdout;
> + return $stdout;
>
> Could it be possible to chomp and return $stderr as well here? It
> seems useful to me to perform sanity checks after calling psql.
Sure, makes sense.
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2015-07-01 14:39:23 | Re: drop/truncate table sucks for large values of shared buffers |
Previous Message | Fujii Masao | 2015-07-01 14:15:19 | Re: Support for N synchronous standby servers - take 2 |