| From: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
|---|---|
| To: | Vik Fearing <vik(dot)fearing(at)dalibo(dot)com> |
| Cc: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, PG Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_system_identifier() |
| Date: | 2013-08-23 13:59:44 |
| Message-ID: | m2siy08q3z.fsf@2ndQuadrant.fr |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Vik Fearing <vik(dot)fearing(at)dalibo(dot)com> writes:
>>> The attached patch implements a pg_system_identifier() function that
>>> exposes it.
>
> It's information about the server that's only accessible through
> pg_controldata. I don't know if that's justification enough, which is
> why I didn't add it to the commitfest yet.
We already have two extensions to expose pg_controldata output at the
SQL level, and I think we should just include the facility in core.
https://github.com/jconway/pg_controldata
http://labs.omniti.com/labs/pgtreats/browser/trunk/contrib/control
Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hannu Krosing | 2013-08-23 15:08:05 | Re: pg_system_identifier() |
| Previous Message | Greg Stark | 2013-08-23 13:58:51 | Re: Does larger i/o size make sense? |