Re: Function pg_get_constraintdef

Alvaro Herrera <alvherre@alvh.no-ip.org>

From: Alvaro Herrera <alvherre@alvh.no-ip.org>

To: Magnus Hagander <magnus@hagander.net>

Cc: Erki Eessaar <erki.eessaar@taltech.ee>, "pgsql-bugs@lists.postgresql.org" <pgsql-bugs@lists.postgresql.org>

Date: 2024-11-27T12:53:07Z

Lists: pgsql-bugs

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Fix pg_get_constraintdef for NOT NULL constraints on domains
- 6e793582bc66 17.3 landed
- 09d09d4297b9 18.0 landed

On 2024-Nov-21, Magnus Hagander wrote:

> I can confirm that fixes it.

Thanks for testing it!

> A quick grep for example shows that CONSTRAINT_TRIGGER is only used in that
> same place, so that should at least be the only case-statement that needs
> them all. But I really don't know enough about that code to comment on
> whether there are other likely places for it :)

I looked around and couldn't find anything either.  I hope we're not
wrong.

Thanks, Erki, for reporting the issue.

-- 
Álvaro Herrera        Breisgau, Deutschland  —  https://www.EnterpriseDB.com/
"No tengo por qué estar de acuerdo con lo que pienso"
                             (Carlos Caszeli)