Re: Exposing PG_VERSION_NUM in pg_config - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: Exposing PG_VERSION_NUM in pg_config
Date
Msg-id CAFj8pRD+GpUjgpFEiUqL=6rcaRR6-anx_f57td758iOKkNqLXQ@mail.gmail.com
Whole thread Raw
In response to Re: Exposing PG_VERSION_NUM in pg_config  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers
<div dir="ltr"><br /><div class="gmail_extra">Review:<br /><br /></div><div class="gmail_extra">1. Discussion - I read
alldiscussion and majority opinion is positive to this patch. I am for this patch too. I had to solve same issues with
Orafceproject. More - this patch is terrible simple - it is just the  publishing already prepared value. <br
/></div><divclass="gmail_extra"><br /></div><div class="gmail_extra">2. There was not any problem with patching,
compilation,testing - It should to have zero impact on PostgreSQL engine.<br /><br /></div><div class="gmail_extra">3.
Irechecked it, and it is working<br /></div><div class="gmail_extra"><br /></div><div class="gmail_extra">I have not
anyobjection, so I'll mark this patch as ready for commit.<br /></div><div class="gmail_extra"><br /></div><div
class="gmail_extra">Regards<br/><br /></div><div class="gmail_extra">Pavel Stehule<br /></div></div> 

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Unneeded NULL-pointer check in FreeSpaceMapTruncateRel
Next
From: "Syed, Rahila"
Date:
Subject: Re: [PROPOSAL] VACUUM Progress Checker.