Re: Preventing abort() and exit() calls in libpq

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Jacob Champion <pchampion(at)vmware(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Daniel Gustafsson <daniel(at)yesql(dot)se>
Subject: Re: Preventing abort() and exit() calls in libpq
Date: 2021-06-30 17:24:26
Message-ID: 18eda75d-af6d-3fc0-03b6-607eff9f392a@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 26.06.21 23:29, Tom Lane wrote:
> After some thought I propose that what we really want is to prevent
> any calls of abort() or exit() from inside libpq. Attached is a
> draft patch to do that.

Could we set this rule up a little bit differently so that it is only
run when the library is built.

Right now, make world on a built tree makes 17 calls to this "nm" line,
and make check-world calls it 81 times. I think once would be enough. ;-)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Paul A Jungwirth 2021-06-30 17:39:00 SQL:2011 application time
Previous Message Peter Eisentraut 2021-06-30 17:13:16 Re: [PATCH] Make jsonapi usable from libpq