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

From: Manuel Rigger <rigger(dot)manuel(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
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 16:33:08
Message-ID: CA+u7OA6UCcipb=LvC6fKeZWYPU6LGzi6HveUsJzDeW9xjbk6wA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi Michael,

Thank you very much for the feedback and pointing me to the patches!
I'm very much looking forward to them being integrated. :)

Best,
Manuel

On Tue, Jul 16, 2019 at 8:01 AM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>
> 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 Andrew Gierth 2019-07-16 17:36:54 Re: BUG #15911: Why no Bcrypt in pg_hba.conf?
Previous Message PG Bug reporting form 2019-07-16 16:26:54 BUG #15912: The units of `autovacuum_vacuum_cost_delay` setting should be documented