Re: pgsql: Prohibit identity columns on typed tables and partitions

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Magnus Hagander <magnus(at)hagander(dot)net>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Cc: PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pgsql: Prohibit identity columns on typed tables and partitions
Date: 2017-12-09 13:45:36
Message-ID: 9b14d7f2-6c90-80af-66d5-d7e075809ea5@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On 12/9/17 05:47, Magnus Hagander wrote:
>
>
> On Sat, Dec 9, 2017 at 8:43 AM, Michael Paquier
> <michael(dot)paquier(at)gmail(dot)com <mailto:michael(dot)paquier(at)gmail(dot)com>> wrote:
>
> On Sat, Dec 9, 2017 at 2:26 AM, Peter Eisentraut <peter_e(at)gmx(dot)net
> <mailto:peter_e(at)gmx(dot)net>> wrote:
> > Prohibit identity columns on typed tables and partitions
> >
> > Those cases currently crash and supporting them is more work then
> > originally thought, so we'll just prohibit these scenarios for now.
>
> +                               (errcode(ERRCODE_FEATURE_NOT_SUPPORTED),
> +                                errmsg("identify columns are not
> supported on partitions")));
> Er... s/identify/identity/. My fault I guess.
>
>
> Spotted the separate report on it first, so a fix has been pushed.

Please also backpatch to PG10.

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Magnus Hagander 2017-12-09 13:47:08 Re: pgsql: Prohibit identity columns on typed tables and partitions
Previous Message Magnus Hagander 2017-12-09 12:45:23 pgsql: Fix regression test output

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2017-12-09 13:47:08 Re: pgsql: Prohibit identity columns on typed tables and partitions
Previous Message Stephen Frost 2017-12-09 13:45:14 Re: Speeding up pg_upgrade