Re: Refactoring: Use soft error reporting for *_opt_error functions

From: Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>
To: Amul Sul <sulamul(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Refactoring: Use soft error reporting for *_opt_error functions
Date: 2025-09-01 11:21:18
Message-ID: CAEZATCXZNZtR6e7WG-qnTSdX33Xmg4Jfxx6xrE-jeAbDywkTXg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, 1 Sept 2025 at 10:36, Amul Sul <sulamul(at)gmail(dot)com> wrote:
>
> I believe we should update all *_opt_error functions to use the new
> soft error reporting infrastructure instead of boolean flags -- did
> the same in the attached patch. I am not sure if this patch should be
> part of that thread[1]. It's a significant improvement in itself, as
> it would make the code more compact and consistent.

Agreed. That does look neater.

Regards,
Dean

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Xuneng Zhou 2025-09-01 11:31:29 Re: Add progressive backoff to XactLockTableWait functions
Previous Message Dmitry Koval 2025-09-01 11:03:58 Re: Add SPLIT PARTITION/MERGE PARTITIONS commands