From: | Rachel Heaton <rachelmheaton(at)gmail(dot)com> |
---|---|
To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
Cc: | Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Jacob Champion <pchampion(at)vmware(dot)com> |
Subject: | Re: [PATCH] Print error when libpq-refs-stamp fails |
Date: | 2021-09-28 15:52:59 |
Message-ID: | CADJcwiUqVGv5geSX5p_oU0OcPBfq_WVrGMsKmQieipbmVT5H5Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Sep 28, 2021 at 6:14 AM Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
>
> Since it's not actually libpq which calls exit (no such patch would ever be
> committed), I think it would be clearer to indicate that a library linked to is
> the culprit. How about something like "libpq must not be linked against any
> library calling exit"?
>
Excellent update to the error message. Patch attached.
Attachment | Content-Type | Size |
---|---|---|
0002-Print-error-when-libpq-refs-stamp-fails.patch | application/octet-stream | 1.1 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Jaime Casanova | 2021-09-28 15:58:53 | Re: FETCH FIRST clause PERCENT option |
Previous Message | Andrew Dunstan | 2021-09-28 15:46:52 | Re: Couldn't we mark enum_in() as immutable? |