From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
---|---|
To: | Bernd Helmle <mailings(at)oopsware(dot)de> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: GUC for data checksums |
Date: | 2013-09-14 22:25:34 |
Message-ID: | 20130914222534.GG4071@awork2.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
On 2013-09-14 18:33:38 +0200, Bernd Helmle wrote:
> Attached is a small patch to add a new GUC to report wether data checksums
> for a particular cluster are enabled. The only way to get this info afaik is
> to look into pg_control and the version number used, but i'd welcome a way
> to access this remotely, too. If there aren't any objections i'll add this
> to the CF.
Looks like a good idea to me. The implementation looks sane as well,
except that I am not sure if we really need to introduce that faux
variable. If the variable cannot be set and we have a SHOW hook, do we
need it?
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Marko Tiikkaja | 2013-09-14 22:26:25 | Re: Assertions in PL/PgSQL |
Previous Message | Andres Freund | 2013-09-14 22:15:24 | Re: INSERT...ON DUPLICATE KEY LOCK FOR UPDATE |