pg.ddx.io pgsql-hackers@postgresql.org mailing list archive
help / color / mirror / Atom feed From: Tom Lane <tgl@sss.pgh.pa.us>
To: Heikki Linnakangas <hlinnaka@iki.fi>
Cc: Soumyadeep Chakraborty <soumyadeep2007@gmail.com>
Cc: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: Refactor pg_rewind code and make it work against a standby
Date: Sun, 15 Nov 2020 01:48:20 -0500
Message-ID: <605973.1605422900@sss.pgh.pa.us> (raw )
In-Reply-To: <95c2ad04-eb6b-7c2e-b751-c65acccd81df@iki.fi >
References: <0c5b3783-af52-3ee5-f8fa-6e794061f70d@iki.fi >
<20200820.173224.2258034742176021277.horikyota.ntt@gmail.com >
<f155aab5-1323-8d0c-9e3b-32703124bf00@iki.fi >
<20200918.164150.1688011206252014871.horikyota.ntt@gmail.com >
<CAE-ML+-uLy_DiS4VSkbsjMEY9ZBob5LqBXPc31_dQ-EsSesgEw@mail.gmail.com >
<4744063e-1a60-1b24-e1b7-7ace5e65f0d2@iki.fi >
<CAE-ML+9NG=HnLq8P_sHM=9UFUPnWbQDSRnmZrMPXONERVJS+zQ@mail.gmail.com >
<da768d3a-dddc-fd3f-4b64-e951a1926bfa@iki.fi >
<95c2ad04-eb6b-7c2e-b751-c65acccd81df@iki.fi >
Not sure if you noticed, but piculet has twice failed the
007_standby_source.pl test that was added by 9c4f5192f:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=piculet&dt=2020-11-15%2006%3A00%3A11
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=piculet&dt=2020-11-13%2011%3A20%3A10
and francolin failed once:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=francolin&dt=2020-11-12%2018%3A57%3A33
These failures look the same:
# Failed test 'table content after rewind and insert: query result matches'
# at t/007_standby_source.pl line 160.
# got: 'in A
# in A, before promotion
# in A, after C was promoted
# '
# expected: 'in A
# in A, before promotion
# in A, after C was promoted
# in A, after rewind
# '
# Looks like you failed 1 test of 3.
[11:27:01] t/007_standby_source.pl ...
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/3 subtests
Now, I'm not sure what to make of that, but I can't help noticing that
piculet uses --disable-atomics while francolin uses --disable-spinlocks.
That leads the mind towards some kind of low-level synchronization
bug ...
regards, tom lane
view thread (18+ messages) latest in thread
Message-ID: <605973.1605422900@sss.pgh.pa.us>
Permalink: ../605973.1605422900@sss.pgh.pa.us/
Also on: postgresql.org/message-id/605973.1605422900@sss.pgh.pa.us
copy link · copy postgr.es
reply 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: tgl@sss.pgh.pa.us, hlinnaka@iki.fi, soumyadeep2007@gmail.com, horikyota.ntt@gmail.com
Subject: Re: Refactor pg_rewind code and make it work against a standby
In-Reply-To: <605973.1605422900@sss.pgh.pa.us>
* 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