Re: BUG #19446: Domain DEFAULT not reflected in system catalogs and information_schema (PG 18.3)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: zheng_xianghang(at)163(dot)com
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19446: Domain DEFAULT not reflected in system catalogs and information_schema (PG 18.3)
Date: 2026-03-30 18:51:08
Message-ID: 2544270.1774896668@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

PG Bug reporting form <noreply(at)postgresql(dot)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

In response to

Browse pgsql-bugs by date

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