Re: PATCH: Report libpq version and configuration

From: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
To: Craig Ringer <craig(dot)ringer(at)enterprisedb(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PATCH: Report libpq version and configuration
Date: 2020-12-28 10:14:24
Message-ID: CAD21AoDxpcXMs7X83LVFw1JQ0fKKCPH+H8Ohcn5DW6QwU=enAQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Craig,

On Wed, Nov 11, 2020 at 1:11 PM Craig Ringer
<craig(dot)ringer(at)enterprisedb(dot)com> wrote:
>
> On Tue, Nov 10, 2020 at 2:22 PM Craig Ringer <craig(dot)ringer(at)enterprisedb(dot)com> wrote:
>>
>>
>> The main things I'd really like to get in place are a way to get the version as an ELF data symbol, and a simple way to ID the binary.
>>
>> So the minimal change would be to declare:
>>
>> const char LIBPQ_VERSION_STR[] = PG_VERSION_STR;
>> const int LIBPQ_VERSION_NUM = PG_VERSION_NUM;
>>
>> then change PQgetVersion() to return LIBPQ_VERSION_NUM and add a PQgetVersionStr() that returns LIBPQ_VERSION_STR.
>>
>> That OK with you?
>
>
> Proposed minimal patch attached.

You sent in your patch, v2-0001-Add-PQlibVersionString-to-libpq.patch
to pgsql-hackers on Nov 11, but you did not post it to the next
CommitFest[1]. If this was intentional, then you need to take no
action. However, if you want your patch to be reviewed as part of the
upcoming CommitFest, then you need to add it yourself before
2021-01-01 AOE[2]. Thanks for your contributions.

Regards,

[1] https://commitfest.postgresql.org/31/
[2] https://en.wikipedia.org/wiki/Anywhere_on_Earth

--
Masahiko Sawada
EnterpriseDB: https://www.enterprisedb.com/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2020-12-28 10:29:21 Re: Table AM modifications to accept column projection lists
Previous Message Masahiko Sawada 2020-12-28 10:11:53 Re: Disable WAL logging to speed up data loading