pg_dump bug for extension owned tables

Found when working against release 12.

Given the following extension:

::::::::::::::
share/postgresql/extension/dummy--1.0.0.sql
::::::::::::::
-- complain if script is sourced in psql, rather than via CREATE EXTENSION
\echo Use "CREATE EXTENSION dummy" to load this file. \quit

CREATE TABLE @extschema(at)(dot)dummytab (
       a int,
       b int,
       c int);
SELECT pg_catalog.pg_extension_config_dump('dummytab', '');

::::::::::::::
share/postgresql/extension/dummy.control
::::::::::::::
# dummy extension
comment = 'dummy'
default_version = '1.0.0'
relocatable = false

and this use of it:

bin/psql -c 'create schema dummy; create extension  dummy schema dummy;
insert into dummy.dummytab values(1,2,3);'

this command segfaults:

bin/pg_dump -a --column-inserts -n dummy

It appears that for extension owned tables tbinfo.attgenerated isn't
being properly populated, so line 2050 in REL_12_STABLE, which is line
2109 in git tip, is failing.

I'm looking for a fix, but if anyone has a quick fix that would be nice :-)

cheers

andrew

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