Re: BUG #17007: server process (PID XXXX) was terminated by signal 11: Segmentation fault

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: varun kamal <kamalvarun2004(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #17007: server process (PID XXXX) was terminated by signal 11: Segmentation fault
Date: 2021-05-15 15:15:05
Message-ID: CAKFQuwaGbVyN6Q6bE0CRCaOAw==tWXifC8Egf+p-R6_MMLFL2A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Saturday, May 15, 2021, varun kamal <kamalvarun2004(at)gmail(dot)com> wrote:

> Dear Tom and David,
>
> Kindly help me to understand below points.
>
> 1. Is it known bug in this particular version (12.2).
> 2. Upgrading to 12.7 will resolve this issue.
>

You are welcome to scan the release notes to figure out whether the
described behavior was seen and fixed in the last year plus. But when we
say releases are unsupported the expectation is that bug reports against
those releases are expected to be ignored (though exceptions do arise).

If you could provide a self-contained reproducible test case I’m sure
someone would be willing to run that against both the older and newer
versions.

David J.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Shay Rojansky 2021-05-15 15:43:21 Re: BUG #16913: GENERATED AS IDENTITY column nullability is affected by order of column properties
Previous Message David Rowley 2021-05-15 14:59:41 Re: BUG #16968: Planner does not recognize optimization