| From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
|---|---|
| To: | Harold Giménez <harold(dot)gimenez(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Changing pg_dump default file format |
| Date: | 2013-11-08 03:01:11 |
| Message-ID: | 527C53F7.9040608@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 11/08/2013 12:53 AM, Harold Giménez wrote:
>
>
> Just a thought: If it's the right thing to do, why not do it in small
> steps?
> For example, couldn't we deprecate the behavior on 9.4, and switch over in
> 9.5? By deprecate I mean a warning message on STDERR making it clear
> they're relying on behavior that is scheduled to change.
I used to like that idea too, but I've since learned the hard way that:
(a) Lots of people only upgrade every two, three, or even more major
versions. I'm dealing with clients on 8.3, and people still pop up on
Stack Overflow with 8.1 sometimes! These people don't ever see the
deprecated phase.
(b) People routinely ignore cron job output. Even important job output.
They won't see the messages, and won't act on them if they do until
something actually breaks.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2013-11-08 03:07:20 | Re: Changing pg_dump default file format |
| Previous Message | Andrew Dunstan | 2013-11-08 02:29:08 | Re: Changing pg_dump default file format |