Re: [PATCH] Rebuild CHECK constraints after generated column SET EXPRESSION

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: Nathan Bossart <nathandbossart(at)gmail(dot)com>
Cc: jian he <jian(dot)universality(at)gmail(dot)com>, Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: [PATCH] Rebuild CHECK constraints after generated column SET EXPRESSION
Date: 2026-07-22 16:15:35
Message-ID: 5be908b7-f543-4d30-a179-a6ea891225c5@eisentraut.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 15.07.26 17:44, Nathan Bossart wrote:
> [RMT hat]
>
> On Wed, Jul 08, 2026 at 08:15:54PM +0200, Peter Eisentraut wrote:
>> Committed with some code beautification editorialization.
>
> This is listed on the v19 open items wiki [0] as an "older bug affecting
> stable branches." Is there more work to do, or can this be moved to the
> "fixed issues" section?
>
> [0] https://wiki.postgresql.org/wiki/PostgreSQL_19_Open_Items

This is a fix for new-in-PG19 functionality, so I think that
classification is wrong.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2026-07-22 16:23:02 Re: pgsql: Move tar detection and compression logic to common.
Previous Message Ants Aasma 2026-07-22 16:09:18 Re: [PATCH] Batched clock sweep to reduce cross-socket atomic contention