Re: BUG #16913: GENERATED AS IDENTITY column nullability is affected by order of column properties

From: Vik Fearing <vik(at)postgresfriends(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Amit Langote <amitlangote09(at)gmail(dot)com>
Cc: pavel(dot)boev(at)invitae(dot)com, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #16913: GENERATED AS IDENTITY column nullability is affected by order of column properties
Date: 2021-03-12 17:21:20
Message-ID: 3fb6c576-182e-e664-f64a-a65a74da85de@postgresfriends.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 3/12/21 4:30 PM, Tom Lane wrote:
> Amit Langote <amitlangote09(at)gmail(dot)com> writes:
>> On Thu, Mar 11, 2021 at 11:37 PM Vik Fearing <vik(at)postgresfriends(dot)org> wrote:
>>> On 3/4/21 3:22 PM, Vik Fearing wrote:
>>>> I can confirm this bug. Attached is a patch to prevent it.
>
>>> Would anybody like to take a look at this?
>
>> Patch looks reasonable to me.
>
> Will push it in a bit.

Thanks, Tom.
--
Vik Fearing

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2021-03-12 19:03:44 BUG #16925: ERROR: invalid DSA memory alloc request size 1073741824 CONTEXT: parallel worker
Previous Message Regina Obe 2021-03-12 16:48:31 RE: BUG #16920: Can't compile PostGIS with MingW64 against PostgreSQL 14 head