Re: future of serial and identity columns

From: Corey Huinker <corey(dot)huinker(at)gmail(dot)com>
To: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: future of serial and identity columns
Date: 2022-10-12 06:22:31
Message-ID: CADkLM=eCmoWJd54TCdrY1Mkmo6W1W_g3LR6pwx-pbmNFxr37BA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>
> 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.
>

I like what I see so far!

Question: the xref refers the reader to sql-createtable, which is a pretty
big page, which could leave the reader lost. Would it make sense to create
a SQL-CREATETABLE-IDENTITY anchor and link to that instead?

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message kuroda.hayato@fujitsu.com 2022-10-12 06:35:32 RE: test_decoding assertion failure for the loss of top-sub transaction relationship
Previous Message Drouvot, Bertrand 2022-10-12 06:17:14 Re: Patch proposal: make use of regular expressions for the username in pg_hba.conf