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

From Alvaro Herrera
Subject Re: Segfault when restoring -Fd dump on current HEAD
Date
Msg-id 20190425190547.GA6690@alvherre.pgsql
Whole thread Raw
In response to Re: Segfault when restoring -Fd dump on current HEAD  (Dmitry Dolgov <9erthalion6@gmail.com>)
Responses Re: Segfault when restoring -Fd dump on current HEAD
List pgsql-hackers
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.

Thanks

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: REINDEX INDEX results in a crash for an index of pg_class since 9.6
Next
From: Alvaro Herrera
Date:
Subject: Re: pg_waldump and PREPARE