Re: cataloguing NOT NULL constraints

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Alexander Lakhin <exclusion(at)gmail(dot)com>, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, Peter Eisentraut <peter(at)eisentraut(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: cataloguing NOT NULL constraints
Date: 2024-02-05 08:51:33
Message-ID: 202402050851.2ktovxwc4irp@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2024-Feb-05, Michael Paquier wrote:

> On Fri, Feb 02, 2024 at 07:00:01PM +0300, Alexander Lakhin wrote:
> > results in:
> > NOTICE:  merging definition of column "i" for child "b"
> > NOTICE:  merging definition of column "i" for child "c"
> > ERROR:  tuple already updated by self
> >
> > (This is similar to bug #18297, but ATExecAddColumn() isn't guilty in this
> > case.)
>
> Still I suspect that the fix should be similar, so I'll go put a coin
> on a missing CCI().

Hmm, let me have a look, I can probably get this one fixed today before
embarking on a larger fix elsewhere in the same feature.

--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
"After a quick R of TFM, all I can say is HOLY CR** THAT IS COOL! PostgreSQL was
amazing when I first started using it at 7.2, and I'm continually astounded by
learning new features and techniques made available by the continuing work of
the development team."
Berend Tober, http://archives.postgresql.org/pgsql-hackers/2007-08/msg01009.php

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Graham Leggett 2024-02-05 08:51:50 Re: Grant read-only access to exactly one database amongst many
Previous Message Yugo NAGATA 2024-02-05 08:22:56 Re: Change COPY ... ON_ERROR ignore to ON_ERROR ignore_row