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

From: "Mike Bayer" <mike_mp(at)zzzcomputing(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: invalid constraint type "n" when using pg_catalog.pg_get_constraintdef() on pg17, regression from pg16
Date: 2024-12-12 15:59:49
Message-ID: e21966fc-db8e-4899-8dca-1cdb95083447@app.fastmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, Dec 12, 2024, at 10:48 AM, Tom Lane wrote:
> "Mike Bayer" <mike_mp(at)zzzcomputing(dot)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

In response to

Browse pgsql-bugs by date

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