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 e4fedac0-3de4-4773-94d3-c391c9e19d63@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  ("David G. Johnston" <david.g.johnston@gmail.com>)
Responses Re: invalid constraint type "n" when using pg_catalog.pg_get_constraintdef() on pg17, regression from pg16
List pgsql-bugs
Tree view

On Thu, Dec 12, 2024, at 9:37 AM, David G. Johnston wrote:
On Thu, Dec 12, 2024 at 7:14 AM David G. Johnston <david.g.johnston@gmail.com> wrote:
On Thursday, December 12, 2024, Mike Bayer <mike_mp@zzzcomputing.com> wrote:

$ psql -U scott -h pg17 test
Password for user scott:
psql (16.3, server 17.2)
WARNING: psql major version 16, server major version 17.
         Some psql features might not work.

This is apparently just such a feature…


My bad, ignore this, I saw this and ended up thinking the complaint was against psql, not the server-internals.

David J.

correct, this is observed using all Python postgresql drivers, I was using psql to make an easy repro




pgsql-bugs by date:

Previous
From: "David G. Johnston"
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: invalid constraint type "n" when using pg_catalog.pg_get_constraintdef() on pg17, regression from pg16