Re: SELECT with COLLATE results in segfault on trunk and 12 Beta 2 - Mailing list pgsql-bugs

From Michael Paquier
Subject Re: SELECT with COLLATE results in segfault on trunk and 12 Beta 2
Date
Msg-id 20190716060147.GD1439@paquier.xyz
Whole thread Raw
In response to Re: SELECT with COLLATE results in segfault on trunk and 12 Beta 2  (Manuel Rigger <rigger.manuel@gmail.com>)
Responses Re: SELECT with COLLATE results in segfault on trunk and 12 Beta 2  (Manuel Rigger <rigger.manuel@gmail.com>)
List pgsql-bugs
On Mon, Jul 15, 2019 at 01:14:27PM +0200, Manuel Rigger wrote:
> Would you consider this bug to be distinct, or is it the same as the
> previous one that I reported?

I think that Tom has the right call here and that we have the same
issue as reported on the other thread.  I have quickly looked at the
set of patches sent by Tomas here:
https://www.postgresql.org/message-id/20190715013425.v2hqfq5ubcbslw67@development

And these are fixing the issues reported on this thread.

> I could not reproduce this on the latest release version, so I assume
> again that this is not a security issue.

Live bugs on non-released versions are not security issues.  They
may become so if they represent an actual security problem (say memory
disclosure with a logged in user, etc.) after v12 is GA though.
--
Michael

Attachment

pgsql-bugs by date:

Previous
From: Michael Paquier
Date:
Subject: Re: BUG #15907: JSON Select Issue
Next
From: Christoph Berg
Date:
Subject: Re: BUG #15896: pg_upgrade from 10-or-earlier: TRAP: FailedAssertion(»!(metad->btm_version >= 3)«