Postgres Pro
Downloads
Home   >   mailing lists

Re: invalid constraint type "n" when using pg_catalog.pg_get_constraintdef() on pg17, regression from pg16 - Mailing list pgsql-bugs

From Tom Lane
Subject Re: invalid constraint type "n" when using pg_catalog.pg_get_constraintdef() on pg17, regression from pg16
Date
Msg-id 652291.1734018520@sss.pgh.pa.us
Whole thread Raw
In response to Re: invalid constraint type "n" when using pg_catalog.pg_get_constraintdef() on pg17, regression from pg16  ("Mike Bayer" <mike_mp@zzzcomputing.com>)
Responses Re: invalid constraint type "n" when using pg_catalog.pg_get_constraintdef() on pg17, regression from pg16
List pgsql-bugs
Tree view 
"Mike Bayer" <mike_mp@zzzcomputing.com> writes:
> correct, this is observed using all Python postgresql drivers, I was using psql to make an easy repro

As Jian said, this was reported and fixed last month.
(I checked that your example works against v17 branch tip.)
Should appear in 17.3.

            regards, tom lane

pgsql-bugs by date:

Previous
From: "Mike Bayer"
Date:
Subject: Re: invalid constraint type "n" when using pg_catalog.pg_get_constraintdef() on pg17, regression from pg16
Next
From: "Mike Bayer"
Date:
Subject: Re: invalid constraint type "n" when using pg_catalog.pg_get_constraintdef() on pg17, regression from pg16