Re: Index Skip Scan - attempting to evalutate patch

From: pguser <pguser(at)diorite(dot)uk>
To: "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Index Skip Scan - attempting to evalutate patch
Date: 2019-06-26 15:47:48
Message-ID: iaJgdpd4atIGk5RXBsAJZ6bZOFAuk3Vy22XlxFkRTwdeBXAwIWVle5rsFhkG_J6CvJj6q95Oek0jm4mlz1PahUQLmXYmiRaGoWNe-lvWwxU=@diorite.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Wednesday, June 26, 2019 4:07 PM, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> wrote:

> That might be dangerous, if there may be differences in contents of
> catalogs. I don't think the patch does that though, and for me it works
> just fine. I can initdb database using current master, create table +
> indexes, do \d. And I can do that with the patch applied too.
>

Well, this is embarrassing.

I repeated all my steps again on my development laptop (Fedora 30, GCC 9.1.1, glibc 2.29.15) and it all works (doesn't segfault, can initdb).

On my Amazon Linux EC2 , (gcc 7.3.1, glibc 2.6.32) it exhibits fault on patched version.

Same steps, same sources.

Got to be build tools/version related on my EC2 instance.

Darn it. Sorry for wasting your time, I will continue to evaluate patch, and be mindful that something, somewhere is sensitive to build tools versions or lib versions.

Many regards

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2019-06-26 16:08:08 Re: mcvstats serialization code is still shy of a load
Previous Message Tom Lane 2019-06-26 15:26:21 Re: mcvstats serialization code is still shy of a load