Re: Reducing opr_sanity test's runtime under CLOBBER_CACHE_ALWAYS

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Reducing opr_sanity test's runtime under CLOBBER_CACHE_ALWAYS
Date: 2021-05-10 22:57:03
Message-ID: CA+hUKG+HnudhwMU1XhHtNy8mH7m2x0pFmpF46ndgtE7pHVGxaw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, May 11, 2021 at 8:52 AM Andres Freund <andres(at)anarazel(dot)de> wrote:
> ... If we did make the check support shared memory *and*
> partitioned tables, I could easily see it be a win for things like
> LockReleaseAll().

For that case, has the idea of maintaining a dlist of local locks been
considered?

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2021-05-10 22:58:01 Re: PG 14 release notes, first draft
Previous Message Alvaro Herrera 2021-05-10 21:17:14 Re: Enhanced error message to include hint messages for redundant options error