Re: BUG #16951: pg_restore segfaults on custom format piped from a different version of PG
KOPOSOV Sergey <sergey.koposov@ed.ac.uk>
From: Sergey KOPOSOV <Sergey.Koposov@ed.ac.uk>
To: "tgl@sss.pgh.pa.us" <tgl@sss.pgh.pa.us>
Cc: "pgsql-bugs@lists.postgresql.org" <pgsql-bugs@lists.postgresql.org>
Date: 2021-03-31T22:52:14Z
Lists: pgsql-bugs
On Wed, 2021-03-31 at 18:47 -0400, Tom Lane wrote:
> This email was sent to you by someone outside the University.
> You should only click on links or attachments if you are certain that the email is genuine and the content is safe.
>
> Sergey KOPOSOV <Sergey.Koposov@ed.ac.uk> writes:
> > I also noticed when I tried to run pg_restore in the debugger the crash doesn't happen.
> > but it does if I pipe it...
>
> I wonder if your platform is helpfully inserting Windows newlines,
> or perhaps removing them, when the data goes through a pipe.
The platform doing the pg_dump (PG12) is debian
And the one doing pg_restore (PG10) is ubuntu.
Also I know for sure when I use pg_restore from postgresql 12 it works fine in the same configuration.
(And I've regularly transferred tables this way from one system to another, it's just I've recently
migrated the debian system from PG11 to PG12 which lead to this segfault.)
S
The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336. Is e buidheann carthannais a th’ ann an Oilthigh Dhùn Èideann, clàraichte an Alba, àireamh clàraidh SC005336.
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Fix pg_restore's misdesigned code for detecting archive file format.
- ec03f2df17a8 14.0 landed
- 84c5e0dd2e73 12.7 landed
- 35421a470de1 13.3 landed
- 2c9b857afbcf 9.6.22 landed
- 25fe401d5350 11.12 landed
- 1b6961c8fec8 10.17 landed