Re: Draft back-branch release notes are up

From: Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org, Peter Geoghegan <pg(at)bowt(dot)ie>
Subject: Re: Draft back-branch release notes are up
Date: 2026-11-08 17:31:56
Message-ID: CAN4CZFNcbA1MLSwNC-47H9KKsMEQD74srnV7m=-7x9DyXkSuew@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, 08 Nov 2026, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> The test query alone would have been fine, but without a
> straightforward repair recipe, I'm not sure how useful it is. I don't
> want to expend a large amount of note space on a problem that likely
> affects very few people. Maybe we could stop at offering the ALTER
> TABLE commands, and leave people to cope with finding any NULLs on
> their own?

Yes, I think even the test query could be enough, and then simply
mentioning that the constraint has to be fixed or dropped.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2026-11-08 17:49:09 Re: Draft back-branch release notes are up
Previous Message Zsolt Parragi 2026-11-08 17:23:50 Re: libpq: Don't read past the end of a message when tracing it