Re: Let's remove DSM_INPL_NONE.

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Let's remove DSM_INPL_NONE.
Date: 2018-02-28 15:54:11
Message-ID: CA+TgmoYx_y0RpCpDMuT491buR4Gg8ASkcKV_Lthu18oCUvrS3w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Feb 27, 2018 at 11:30 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I'd be in favor of having some normally-ifdef'd-out facility for causing
> failures of this kind. (As I mentioned upthread, I do not think "always
> fail" is sufficient.) That's very different from having a user-visible
> option, though. We don't expose a GUC that enables CLOBBER_FREED_MEMORY,
> to take a relevant example.

Sure. Feel free to propose something you like.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David Steele 2018-02-28 15:55:10 PATCH: Exclude temp relations from base backup
Previous Message Peter Eisentraut 2018-02-28 15:43:43 Re: Kerberos test suite