| From: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
|---|---|
| To: | Peter Geoghegan <pg(at)heroku(dot)com> |
| Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, David Fetter <david(at)fetter(dot)org>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, pgsql-committers(at)postgresql(dot)org, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] Re: pgsql: Add a GUC to report whether data page checksums are enabled. |
| Date: | 2014-02-20 09:00:35 |
| Message-ID: | 5305C433.6070606@vmware.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On 02/20/2014 04:15 AM, Peter Geoghegan wrote:
> On Wed, Feb 19, 2014 at 4:49 PM, Michael Paquier
> <michael(dot)paquier(at)gmail(dot)com> wrote:
>>> +1 for back-patching.
>> Back-patching would be interesting for existing applications, but -1
>> as it is a new feature :)
>
> I think that it rises to the level of an omission in 9.3 that now
> requires correction. Many of our users couldn't run pg_controldata
> even if they'd heard of it...
We seem to have +Many against -1, so back-patched it now.
- Heikki
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2014-02-20 09:00:36 | Re: pgsql: Further code review for pg_lsn data type. |
| Previous Message | Heikki Linnakangas | 2014-02-20 08:59:53 | pgsql: Improve comment on setting data_checksum GUC. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashutosh Bapat | 2014-02-20 09:02:16 | Re: Selecting large tables gets killed |
| Previous Message | amul sul | 2014-02-20 08:49:13 | Re: Selecting large tables gets killed |