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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Mike Bayer" <mike_mp(at)zzzcomputing(dot)com>
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:48:40
Message-ID: 652291.1734018520@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

"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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Mike Bayer 2024-12-12 15:59:49 Re: invalid constraint type "n" when using pg_catalog.pg_get_constraintdef() on pg17, regression from pg16
Previous Message Mike Bayer 2024-12-12 14:55:08 Re: invalid constraint type "n" when using pg_catalog.pg_get_constraintdef() on pg17, regression from pg16