Re: DSM robustness failure (was Re: Peripatus/failures)

From: Larry Rosenman <ler(at)lerctr(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Subject: Re: DSM robustness failure (was Re: Peripatus/failures)
Date: 2018-10-18 01:12:10
Message-ID: 20181018011210.7stfowlkp23cmlt5@ler-imac.local
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Oct 17, 2018 at 08:55:09PM -0400, Tom Lane wrote:
> Larry Rosenman <ler(at)lerctr(dot)org> writes:
> > On Wed, Oct 17, 2018 at 08:10:28PM -0400, Tom Lane wrote:
> >> However, I'm still slightly interested in how it
> >> was that that broke DSM so thoroughly ... I pulled down your version of
> >> python2.7 and will see if that reproduces it.
>
> > It was built on a previous alpha, so who knows what the differing
> > compiler/libs/kernel/etc did. The options used did *NOT* change, just
> > the userland used to compile it. (I.E. that package, running on
> > ALPHA10 is what broke).
>
> Hm. I forcibly installed your package over the regular one using
> pkg add -f python27-2.7.15.txz
> and rebuilt PG, and what I get is a failure in the plpython regression
> test, but no crash. So I'm still confused.

Hell if I know. I've cleaned up my environment (old, broken, etc
stuff), but who knows whats broken what where.

Not sure how to get back to the "broken" state :(

--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 214-642-9640 E-Mail: ler(at)lerctr(dot)org
US Mail: 5708 Sabbia Drive, Round Rock, TX 78665-2106

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2018-10-18 01:17:14 Re: DSM robustness failure (was Re: Peripatus/failures)
Previous Message James Coleman 2018-10-18 01:01:12 Re: pageinspect: add tuple_data_record()