From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Haas <robertmhaas@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: pgsql: Modify pg_basebackup to use a new COPY subprotocol for base back
Date: Tue, 18 Jan 2022 16:36:46 -0500
Message-ID: <412464.1642541806@sss.pgh.pa.us> (raw)
In-Reply-To: <CA+TgmoYx5=1A2K9JYV-9zdhyokU4KKTyNQ9q7CiXrX=YBBMWVw@mail.gmail.com>
References: <E1n9tZJ-00058I-Nd@gemulon.postgresql.org>
<CA+TgmoYx5=1A2K9JYV-9zdhyokU4KKTyNQ9q7CiXrX=YBBMWVw@mail.gmail.com>
Robert Haas <robertmhaas@gmail.com> writes:
> Andres pointed out to me that longfin is sad:
> 2022-01-18 14:52:35.484 EST [82470:4] LOG: server process (PID 82487)
> was terminated by signal 4: Illegal instruction: 4
> Tom, any chance you can get a stack trace?
Hmm, I'd assumed that was just a cosmic ray or something.
I'll check if it reproduces, though.
regards, tom lane
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-committers@postgresql.org
Cc: tgl@sss.pgh.pa.us, robertmhaas@gmail.com, pgsql-hackers@lists.postgresql.org
Subject: Re: pgsql: Modify pg_basebackup to use a new COPY subprotocol for base back
In-Reply-To: <412464.1642541806@sss.pgh.pa.us>
References: <E1n9tZJ-00058I-Nd@gemulon.postgresql.org> <CA+TgmoYx5=1A2K9JYV-9zdhyokU4KKTyNQ9q7CiXrX=YBBMWVw@mail.gmail.com> <412464.1642541806@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