Horton
Menu

Re: BUG #16951: pg_restore segfaults on custom format piped from a different version of PG

Tom Lane <tgl@sss.pgh.pa.us>

View thread
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Justin Pryzby <pryzby@telsasoft.com>
Cc: Sergey KOPOSOV <Sergey.Koposov@ed.ac.uk>, pgsql-bugs@lists.postgresql.org
Date: 2021-04-01T18:13:38Z
Lists: pgsql-bugs 
Justin Pryzby <pryzby@telsasoft.com> writes:
> On Thu, Apr 01, 2021 at 11:39:33AM -0400, Tom Lane wrote:
>> Will fix, thanks for the report!

> Yes, thank you both.  I've run into this recently but for some reason I thought
> it was fixed.  It probably also explains this one from 2014.
> https://www.postgresql.org/message-id/20141206061151.GA725@telsasoft.com

Yeah, this does look suspiciously like it explains some past reports
that we failed to reproduce, likely because it didn't occur to us that
reading the file from a non-seekable source would make a difference.

Thanks to Sergey for beating me over the head till I didn't dismiss
it anymore ;-)

			regards, tom lane

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Fix pg_restore's misdesigned code for detecting archive file format.