Re: Segfault when restoring -Fd dump on current HEAD - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Segfault when restoring -Fd dump on current HEAD
Date
Msg-id 20190425195406.ykcfgv3barkdbpfp@alap3.anarazel.de
Whole thread Raw
In response to Re: Segfault when restoring -Fd dump on current HEAD  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: Segfault when restoring -Fd dump on current HEAD
List pgsql-hackers
Hi,

On 2019-04-25 15:05:47 -0400, Alvaro Herrera wrote:
> On 2019-Mar-10, Dmitry Dolgov wrote:
> 
> > Then I guess we need to add the attached patch on top of a pg_dump support for
> > table am. It contains changes to use NULL as a default value for owner / defn /
> > dropStmt (exactly what we've changed back in 19455c9f56), and doesn't crash,
> > since K_VERS is different.
> 
> I think this is an open item; we were supposed to do it right after
> 3b925e905de3, but failed to notice.
> 
> Would anybody be too upset if I push this patch now?  CC'ed RMT.

I think that'd make sense. The rest of the RMT probably isn't awake
however, so I think it'd be good to give them 24h to object.

Greetings,

Andres Freund



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: REINDEX INDEX results in a crash for an index of pg_class since9.6
Next
From: Tom Lane
Date:
Subject: Re: REINDEX INDEX results in a crash for an index of pg_class since 9.6