BUG #19074: pg_dump from v18 loses the NOT NULL flag in the inherited table field when dumping v17-databases

The following bug has been logged on the website:

Bug reference: 19074
Logged by: Andrew Bille
Email address: andrewbille(at)gmail(dot)com
PostgreSQL version: 18.0
Operating system: Ubuntu 20.04
Description:

Hello.

In 17.6, we're creating tables:

CREATE TABLE p (a integer);
CREATE TABLE c () INHERITS (p);
ALTER TABLE ONLY c ALTER COLUMN a SET NOT NULL;

17/bin/pg_dump test returns:

....
CREATE TABLE public.p (
a integer
);

ALTER TABLE public.p OWNER TO andrew;

--
-- Name: c; Type: TABLE; Schema: public; Owner: andrew
--

CREATE TABLE public.c (
)
INHERITS (public.p);
ALTER TABLE ONLY public.c ALTER COLUMN a SET NOT NULL;
....

REL_18_0, REL_18_STABLE, master
master/bin/pg_dump test produces:

...
CREATE TABLE public.p (
a integer
);

ALTER TABLE public.p OWNER TO andrew;

--
-- Name: c; Type: TABLE; Schema: public; Owner: Andrew
--

CREATE TABLE public.c (
)
INHERITS (public.p);

ALTER TABLE public.c OWNER TO andrew;

--
-- Data for Name: c; Type: TABLE DATA; Schema: public; Owner: Andrew
--

COPY public.c (a) FROM stdin;
\.
...

and loses NOT NULL in the inherited table

Regards, Andrew