Re: Sigh, my old HPUX box is totally broken by DSM patch

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Sigh, my old HPUX box is totally broken by DSM patch
Date: 2013-10-23 16:15:35
Message-ID: 20131023161535.GM2706@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

* Robert Haas (robertmhaas(at)gmail(dot)com) wrote:
> On Wed, Oct 23, 2013 at 11:35 AM, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> > Would this make sense as a configure-time check, rather than initdb, to
> > try blocking SIGSYS and checking for an ENOSYS from shm_open()? Seems
> > preferrable to do that in a configure check rather than initdb.
>
> I don't see why. It's a run-time behavior; the build system may not
> be where the binaries will ultimately run.

I suppose, just need to be more cautious when blocking signals in initdb
than in a configure-time check, of course.

Thanks,

Stephen

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2013-10-23 16:20:38 Re: Add min and max execute statement time in pg_stat_statement
Previous Message Robert Haas 2013-10-23 15:58:02 Re: Commitfest II CLosed