From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Magnus Hagander <magnus@hagander.net>
Cc: Erki Eessaar <erki.eessaar@taltech.ee>
Cc: pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>
Subject: Re: Function pg_get_constraintdef
Date: Wed, 27 Nov 2024 13:53:07 +0100
Message-ID: <202411271253.mo4fyclwupqg@alvherre.pgsql> (raw)
In-Reply-To: <CABUevExn=jj1Jd6By8RpAxXJ91kp1UHQzB=WpQtPf9hhaY45Qw@mail.gmail.com>
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)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: alvherre@alvh.no-ip.org, magnus@hagander.net, erki.eessaar@taltech.ee, pgsql-bugs@lists.postgresql.org
Subject: Re: Function pg_get_constraintdef
In-Reply-To: <202411271253.mo4fyclwupqg@alvherre.pgsql>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox