| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | jian he <jian(dot)universality(at)gmail(dot)com> |
| Cc: | Kirill Reshke <reshkekirill(at)gmail(dot)com>, Peter Eisentraut <peter(at)eisentraut(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: CREATE SCHEMA ... CREATE DOMAIN support |
| Date: | 2026-04-05 18:42:26 |
| Message-ID: | 841583.1775414546@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Apropos of the question of how much rearrangement functionality the
SQL spec actually asks for, I was interested to come across this entry
in SQL:2021's Table 43 — Feature taxonomy and definition for mandatory
features:
Feature ID Feature Name Feature Description
F311-01 CREATE SCHEMA — Subclause 11.1, “<schema definition>”:
Support for circular references in that <refer-
ential constraint definition>s in two different
<table definition>s may reference columns in
the other table
We already claim support for F311-01 in sql_features.txt, but based
on this entry I'd have to say that's a lie. However, (a) the current
patchset fixes that, and (b) this seems like good evidence in support
of the idea that circular foreign keys are the only aspect of the
business that anyone cares about.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lukas Fittl | 2026-04-05 18:51:49 | Fix Heap Blocks accumulation for Parallel Bitmap Heap Scan |
| Previous Message | Heikki Linnakangas | 2026-04-05 18:35:06 | Re: Better shared data structure management and resizable shared data structures |