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 Mike Bayer
Subject Re: invalid constraint type "n" when using pg_catalog.pg_get_constraintdef() on pg17, regression from pg16
Date
Msg-id e21966fc-db8e-4899-8dca-1cdb95083447@app.fastmail.com
Whole thread Raw
In response to Re: invalid constraint type "n" when using pg_catalog.pg_get_constraintdef() on pg17, regression from pg16  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Tree view 

On Thu, Dec 12, 2024, at 10:48 AM, Tom Lane wrote:
> "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

thanks for double checking!

- mike

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: invalid constraint type "n" when using pg_catalog.pg_get_constraintdef() on pg17, regression from pg16
Next
From: Tom Lane
Date:
Subject: Re: "memory exhausted" in query parser/simplifier for many nested parentheses