From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Dump pageinspect to 1.2: page_header with pg_lsn datatype |
Date: | 2014-02-25 20:45:03 |
Message-ID: | 20140225204503.GZ4759@eldon.alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Robert Haas escribió:
> On Mon, Feb 24, 2014 at 9:34 AM, Alvaro Herrera
> <alvherre(at)2ndquadrant(dot)com> wrote:
> > Yeah, erroring out seems good enough. Particularly if you add a hint
> > saying "please upgrade the extension".
>
> In past instances where this has come up, we have actually made the
> .so backward-compatible. See pg_stat_statements in particular. I'd
> prefer to keep to that precedent here.
But pg_stat_statement is a user tool which is expected to have lots of
use, and backwards compatibility concerns because of people who might
have written tools on top of it. Not so with pageinspect. I don't
think we need to put in the same amount of effort. (Even though,
really, it's probably not all that difficult to support both cases. I
just don't see the point.)
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Alex Hunsaker | 2014-02-25 20:46:30 | Re: BUG #9223: plperlu result memory leak |
Previous Message | Robert Haas | 2014-02-25 20:40:39 | Re: Dump pageinspect to 1.2: page_header with pg_lsn datatype |