Re: A generated column cannot be part of a partition key

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Diego Stammerjohann <diegostammer(at)gmail(dot)com>
Cc: Francisco Olarte <folarte(at)peoplecall(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: A generated column cannot be part of a partition key
Date: 2024-07-23 14:51:06
Message-ID: 64060b2a-1f93-48c4-b042-baf0db6239fc@eisentraut.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 23.07.24 16:18, David G. Johnston wrote:
> On Tuesday, July 23, 2024, Diego Stammerjohann <diegostammer(at)gmail(dot)com
> <mailto:diegostammer(at)gmail(dot)com>> wrote:
>
> So, for me, it would be good to have in some place the information
> that an IDENTITY column is not a GENERATED column. That's what
> caused confusion to me.
>
>
> Yeah, 5.3 defines what generated columns are and does not include
> identity.  But nothing in Chapter 5 discusses identity which seems like
> a bug if Chapter 5 is intended be the official reference for concepts.

This has been changed in the documentation for PG 17. There are now
separate sections for identity columns and generated columns:

https://www.postgresql.org/docs/17/ddl-identity-columns.html
https://www.postgresql.org/docs/17/ddl-generated-columns.html

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2024-07-23 15:37:53 BUG #18551: pg_basebackup uses out-of-bounds memory and a segment error occurs during backup
Previous Message David G. Johnston 2024-07-23 14:18:48 Re: A generated column cannot be part of a partition key