Re: SELECT with COLLATE results in segfault on trunk and 12 Beta 2

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Manuel Rigger <rigger(dot)manuel(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>
Subject: Re: SELECT with COLLATE results in segfault on trunk and 12 Beta 2
Date: 2019-07-16 06:01:47
Message-ID: 20190716060147.GD1439@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Christoph Berg 2019-07-16 08:13:46 Re: BUG #15896: pg_upgrade from 10-or-earlier: TRAP: FailedAssertion(»!(metad->btm_version >= 3)«
Previous Message Michael Paquier 2019-07-16 04:49:56 Re: BUG #15907: JSON Select Issue