From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
---|---|
To: | Euler Taveira <euler(at)timbira(dot)com(dot)br>, Francisco Olarte <folarte(at)peoplecall(dot)com> |
Cc: | José Luis Viejo <jlviejo(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: identity not working with inherited table |
Date: | 2019-05-13 16:28:01 |
Message-ID: | 0c4f3c9d-753b-1985-48a9-03fdc782d1d8@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On 2019-05-06 03:46, Euler Taveira wrote:
> Em dom, 5 de mai de 2019 às 08:16, Francisco Olarte
> <folarte(at)peoplecall(dot)com> escreveu:
>>
>> "If a column in the parent table is an identity column, that property
>> is not inherited. A column in the child table can be declared identity
>> column if desired."
>>
> Although, it is documented, it seems inconsistent with sequence
> behavior (child table inherits sequences). Since sequences are
> inherited I think identity columns (that use implicit sequences)
> should be inherited as well. It seems an oversight in the current
> implementation, however, I see it as a new feature.
Some of the semantics of this would not be entirely clear. Who would
own the sequence? What happens when you drop the identity property from
the inheritance root or an inheritance child? It's probably doable, but
it would need some serious thinking.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2019-05-13 17:48:18 | Re: PostgreSQL 9.3.5 substring(text from pattern for escape) bug |
Previous Message | Tom Lane | 2019-05-13 13:59:05 | Re: PostgreSQL 9.3.5 substring(text from pattern for escape) bug |