Re: pgsql: Modify pg_basebackup to use a new COPY subprotocol for base back

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: pgsql: Modify pg_basebackup to use a new COPY subprotocol for base back
Date: 2022-01-18 20:54:19
Message-ID: CA+TgmoYx5=1A2K9JYV-9zdhyokU4KKTyNQ9q7CiXrX=YBBMWVw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On Tue, Jan 18, 2022 at 1:51 PM Robert Haas <rhaas(at)postgresql(dot)org> wrote:
> Modify pg_basebackup to use a new COPY subprotocol for base backups.

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
2022-01-18 14:52:35.484 EST [82470:5] DETAIL: Failed process was
running: BASE_BACKUP ( LABEL 'pg_basebackup base backup', PROGRESS,
CHECKPOINT 'fast', MANIFEST 'yes', TARGET 'client')

Unfortunately, I can't reproduce this locally, even with COPT=-Wall
-Werror -fno-omit-frame-pointer -fsanitize-trap=alignment
-Wno-deprecated-declarations -DWRITE_READ_PARSE_PLAN_TREES
-DSTRESS_SORT_INT_MIN -DENFORCE_REGRESSION_TEST_NAME_RESTRICTIONS.

Tom, any chance you can get a stack trace?

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2022-01-18 21:36:46 Re: pgsql: Modify pg_basebackup to use a new COPY subprotocol for base back
Previous Message Andres Freund 2022-01-18 20:40:12 Re: pgsql: Test replay of regression tests, attempt II.

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2022-01-18 21:01:01 Re: Schema variables - new implementation for Postgres 15
Previous Message Mark Dilger 2022-01-18 20:51:46 Re: CREATEROLE and role ownership hierarchies