Request a Demo
Home   >   mailing lists

Re: BUG #19446: Domain DEFAULT not reflected in system catalogs and information_schema (PG 18.3) - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #19446: Domain DEFAULT not reflected in system catalogs and information_schema (PG 18.3)
Date
Msg-id 2544270.1774896668@sss.pgh.pa.us
Whole thread Raw
In response to BUG #19446: Domain DEFAULT not reflected in system catalogs and information_schema (PG 18.3)  (PG Bug reporting form <noreply@postgresql.org>)
List pgsql-bugs
Tree view 
PG Bug reporting form <noreply@postgresql.org> writes:
> When a column uses a domain with DEFAULT value, all system catalogs fail to
> reflect the default:
> - pg_attribute.atthasdef = false
> - No entries in pg_attrdef
> - information_schema.columns.column_default is empty
> But the default value works correctly at runtime.
> This is a metadata bug.

This is a duplicate of #19445, and is no more valid than that is.
Please stop harassing us with poorly-researched bug reports.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #19445: Domain DEFAULT not recorded in pg_attrdef (atthasdef false) in PostgreSQL 18.3
Next
From: Tom Lane
Date:
Subject: Re: BUG #19443: GIN jsonb_path_ops index not used when many rows contain nested null values (PostgreSQL 18.3)