From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | Erki Eessaar <erki(dot)eessaar(at)taltech(dot)ee>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Function pg_get_constraintdef |
Date: | 2024-11-27 12:53:07 |
Message-ID: | 202411271253.mo4fyclwupqg@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
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)
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2024-11-27 14:54:15 | Re: Build failure with GCC 15 (defaults to -std=gnu23) |
Previous Message | Andrew Dunstan | 2024-11-27 12:52:16 | Re: pg_rewind fails on Windows where tablespaces are used |