Re: Strange failure in LWLock on skink in REL9_5_STABLE

From: Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Strange failure in LWLock on skink in REL9_5_STABLE
Date: 2018-11-06 05:45:02
Message-ID: CAEepm=38f0cq4xteGon-7iFUYsPQfbvmzA__28E3i9s1WinFXQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Nov 6, 2018 at 6:15 PM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> On Tue, Nov 06, 2018 at 05:29:36PM +1300, Thomas Munro wrote:
> > Thanks. Pushed to master only.
>
> Just a wild idea while this thread is hot: could we add in the
> description of the broken APIs or in their headers more information
> about how to not use them so as users are warned if trying to use them
> in certain circumstances? This idea is just for the stable branches.

Like this?

--
Thomas Munro
http://www.enterprisedb.com

Attachment Content-Type Size
deprecated.patch application/octet-stream 2.7 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2018-11-06 06:06:29 Re: csv format for psql
Previous Message Michael Paquier 2018-11-06 05:15:51 Re: Strange failure in LWLock on skink in REL9_5_STABLE