| From: | Ian Barwick <ian(dot)barwick(at)2ndquadrant(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz>, Ron <ronljohnsonjr(at)gmail(dot)com> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Tables(s) that feed pg_controldata |
| Date: | 2018-12-10 03:16:32 |
| Message-ID: | cf0c9039-feb5-2a83-4a92-4d8c0725fd5d@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 12/10/2018 11:50 AM, Michael Paquier wrote:
> On Sun, Dec 09, 2018 at 08:10:57PM -0600, Ron wrote:
>> On 12/09/2018 07:51 PM, Ian Barwick wrote:
>>> but you're out of luck for 9.2. The only option to query the desired
>>> values via
>>> SQL would be to write an extension which reads pg_controldata
>>> (possibly as a backport of the above-mentioned functions).
>>
>> Thanks. grep(1) and cut(1) make an adequate work-around.
>
> Perhaps. Even with that, writing an extension for 9.2 would require
> copy-pasting a lot of code from pg_controldata.c and taking as well the
> code which has been introduced for the various control functions.
> Dirty, still doable.
I've got some code which does just that to read pg_control as far
back as 9.3, and it is indeed not pretty ;).
Regards
Ian Barwick
--
Ian Barwick http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Arthur Zakirov | 2018-12-10 07:50:04 | Re: pg_ctl kill INT vs. pg_cancel_backend |
| Previous Message | Ron | 2018-12-10 03:13:57 | Re: Tables(s) that feed pg_controldata |