Re: alternative to PG_CATCH

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>
Subject: Re: alternative to PG_CATCH
Date: 2019-11-04 10:17:25
Message-ID: fc203f54-b56a-da1e-549d-2ab6621bdb1d@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2019-11-02 15:36, Tom Lane wrote:
> I hadn't actually tested this patch before commit, but now that
> it's in, I'm seeing assorted compiler warnings:

I've fixed the ones that I could reproduce on CentOS 6. I haven't seen
any on a variety of newer systems.

It's not clear why only a handful of cases cause warnings, but my guess
is that the functions are above some size/complexity threshold beyond
which those older compilers give up doing a full analysis.

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2019-11-04 10:26:00 Re: cost based vacuum (parallel)
Previous Message vignesh C 2019-11-04 10:16:48 Re: PATCH: logical_work_mem and logical streaming of large in-progress transactions