Re: Simplifying our Trap/Assert infrastructure

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Nathan Bossart <nathandbossart(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Simplifying our Trap/Assert infrastructure
Date: 2022-10-31 09:02:35
Message-ID: f64365b1-d5f9-ef83-41fe-404810f10e5a@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 31.10.22 01:04, Michael Paquier wrote:
> On Fri, Oct 28, 2022 at 09:36:23AM +0200, Peter Eisentraut wrote:
>> Would there be a use for that? It's currently only used in the atomics
>> code.
>
> Yep, but they would not trigger when using atomics in the frontend
> code. We don't have any use for that in core on HEAD, still that
> could be useful for some external frontend code? Please see the
> attached.

I don't think we need separate definitions for frontend and backend,
since the contained Assert() will take care of the difference. So the
attached would be simpler.

Attachment Content-Type Size
0001-Make-AssertPointerAlignment-available-to-frontend-co.patch text/plain 1.4 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Etsuro Fujita 2022-10-31 09:27:53 Error for row-level triggers with transition tables on partitioned tables
Previous Message Etsuro Fujita 2022-10-31 08:50:02 Re: Fast COPY FROM based on batch insert