On Sat, Sep 2, 2017 at 12:03 AM, Alvaro Herrera wrote:
> Michael Paquier wrote:
>> On Mon, Aug 28, 2017 at 8:25 AM, Michael Paquier
>> wrote:
>> > Today's run has finished with the same failure:
>> > https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=dangomushi&dt=2017-08-27%2018%3A00%3A13
>
Michael Paquier wrote:
> On Mon, Aug 28, 2017 at 8:25 AM, Michael Paquier
> wrote:
> > Today's run has finished with the same failure:
> > https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=dangomushi&dt=2017-08-27%2018%3A00%3A13
> > Attached is a patch to make this code path wait that the tr
On 31 August 2017 at 12:54, Simon Riggs wrote:
>> The above-described topic is currently a PostgreSQL 10 open item. Simon,
>> since you committed the patch believed to have created it, you own this open
>> item. If some other commit is more relevant or if this does not belong as a
>> v10 open i
On 27 August 2017 at 03:32, Noah Misch wrote:
> On Fri, Aug 25, 2017 at 12:09:00PM +0200, Petr Jelinek wrote:
>> On 24/08/17 19:54, Tom Lane wrote:
>> > sungazer just failed with
>> >
>> > pg_recvlogical exited with code '256', stdout '' and stderr
>> > 'pg_recvlogical: could not send replication
On Tue, Aug 29, 2017 at 08:44:42PM +0900, Michael Paquier wrote:
> On Mon, Aug 28, 2017 at 8:25 AM, Michael Paquier
> wrote:
> > Today's run has finished with the same failure:
> > https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=dangomushi&dt=2017-08-27%2018%3A00%3A13
> > Attached is a pat
On Sun, Aug 27, 2017 at 02:32:49AM +, Noah Misch wrote:
> On Fri, Aug 25, 2017 at 12:09:00PM +0200, Petr Jelinek wrote:
> > On 24/08/17 19:54, Tom Lane wrote:
> > > sungazer just failed with
> > >
> > > pg_recvlogical exited with code '256', stdout '' and stderr
> > > 'pg_recvlogical: could n
On Mon, Aug 28, 2017 at 8:25 AM, Michael Paquier
wrote:
> Today's run has finished with the same failure:
> https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=dangomushi&dt=2017-08-27%2018%3A00%3A13
> Attached is a patch to make this code path wait that the transaction
> has been replayed. We
On 28/08/17 01:36, Michael Paquier wrote:
> On Sun, Aug 27, 2017 at 6:32 PM, Petr Jelinek
> wrote:
>> Attached should fix this.
>
> +$node_master->poll_query_until('postgres',
> +"SELECT EXISTS (SELECT 1 FROM pg_replication_slots WHERE slot_name =
> 'test_slot' AND active_pid IS NULL)"
> +)
> +
On Mon, Aug 28, 2017 at 8:33 AM, Tom Lane wrote:
> Michael Paquier writes:
>> Attached is a patch to make this code path wait that the transaction
>> has been replayed. We could use as well synchronous_commit = apply,
>> but I prefer the solution of this patch with a wait query.
>
> Petr proposed
On Sun, Aug 27, 2017 at 6:32 PM, Petr Jelinek
wrote:
> Attached should fix this.
+$node_master->poll_query_until('postgres',
+"SELECT EXISTS (SELECT 1 FROM pg_replication_slots WHERE slot_name =
'test_slot' AND active_pid IS NULL)"
+)
+ or die "slot never became inactive";
+
$stdout_recv = $nod
Michael Paquier writes:
> Attached is a patch to make this code path wait that the transaction
> has been replayed. We could use as well synchronous_commit = apply,
> but I prefer the solution of this patch with a wait query.
Petr proposed a different patch to fix the same problem at
https://www.
On Sun, Aug 27, 2017 at 3:34 PM, Michael Paquier
wrote:
> On Sun, Aug 27, 2017 at 12:03 PM, Tom Lane wrote:
>> contains exactly no means of ensuring that the master's transaction has
>> been replayed on the standby before we check for its results. It's not
>> real clear why it seems to work 99.9
On 27/08/17 04:32, Noah Misch wrote:
> On Fri, Aug 25, 2017 at 12:09:00PM +0200, Petr Jelinek wrote:
>> On 24/08/17 19:54, Tom Lane wrote:
>>> sungazer just failed with
>>>
>>> pg_recvlogical exited with code '256', stdout '' and stderr
>>> 'pg_recvlogical: could not send replication command "STAR
On Sun, Aug 27, 2017 at 12:03 PM, Tom Lane wrote:
> And *another* replication test race condition just now:
>
> https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=dangomushi&dt=2017-08-26%2019%3A37%3A08
>
> As best I can interpret this, it's pointing out that this bit in
> src/test/recovery/t
And *another* replication test race condition just now:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=dangomushi&dt=2017-08-26%2019%3A37%3A08
As best I can interpret this, it's pointing out that this bit in
src/test/recovery/t/009_twophase.pl:
$cur_master->psql(
'postgres', "
On Fri, Aug 25, 2017 at 12:09:00PM +0200, Petr Jelinek wrote:
> On 24/08/17 19:54, Tom Lane wrote:
> > sungazer just failed with
> >
> > pg_recvlogical exited with code '256', stdout '' and stderr
> > 'pg_recvlogical: could not send replication command "START_REPLICATION SLOT
> > "test_slot" LOG
On 24/08/17 19:54, Tom Lane wrote:
> sungazer just failed with
>
> pg_recvlogical exited with code '256', stdout '' and stderr 'pg_recvlogical:
> could not send replication command "START_REPLICATION SLOT "test_slot"
> LOGICAL 0/0 ("include-xids" '0', "skip-empty-xacts" '1')": ERROR:
> replica
sungazer just failed with
pg_recvlogical exited with code '256', stdout '' and stderr 'pg_recvlogical:
could not send replication command "START_REPLICATION SLOT "test_slot" LOGICAL
0/0 ("include-xids" '0', "skip-empty-xacts" '1')": ERROR: replication slot
"test_slot" is active for PID 8913148
18 matches
Mail list logo
