Re: future of serial and identity columns

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: future of serial and identity columns
Date: 2022-10-11 07:59:58
Message-ID: b447f582-8e4b-6d61-45ad-7aabec4743f4@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 04.10.22 09:41, Peter Eisentraut wrote:
> Attached is a demo patch how the implementation of this change would
> look like.  This creates a bunch of regression test failures, but
> AFAICT, those are mainly display differences and some very peculiar test
> setups that are intentionally examining some edge cases.  These would
> need to be investigated in more detail, of course.

The feedback was pretty positive, so I dug through all the tests to at
least get to the point where I could see the end of it. The attached
patch 0001 is the actual code and documentation changes. The 0002 patch
is just tests randomly updated or disabled to make the whole suite pass.
This reveals that there are a few things that would warrant further
investigation, in particular around extensions and partitioning. To be
continued.

Attachment Content-Type Size
v2-0001-WIP-Change-serial-types-to-map-to-identity-column.patch text/plain 27.1 KB
v2-0002-FIXME-various-tests-that-still-need-to-be-looked-.patch text/plain 35.8 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Aleksander Alekseev 2022-10-11 08:02:51 Re: Add common function ReplicationOriginName.
Previous Message Amit Langote 2022-10-11 07:37:13 Re: Eliminating SPI from RI triggers - take 2