From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, josh(at)agliodbs(dot)com, pgsql-docs(at)postgresql(dot)org |
Subject: | Re: [pgsql-advocacy] Avoiding upgrade backlash |
Date: | 2007-11-17 21:05:50 |
Message-ID: | 200711172105.lAHL5oV02191@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy pgsql-docs |
Joshua D. Drake wrote:
> Tom Lane wrote:
> > "Joshua D. Drake" <jd(at)commandprompt(dot)com> writes:
> >> Honestly, I think you are underestimating this problem.
> >
>
> > I fail to see why this is a major problem; and merely asserting that
> > it is one isn't going to change my mind. Can you point to something
> > like a major application that will be broken and can't easily be fixed?
>
> SQL-Ledger/LedgerSMB
>
> What I find interesting is that I (and Josh) are getting push back and
> all we are trying to do is be a little louder about the change.
Adding extra warnings/notices is not a zero-cost action so there has to
be justification to do it. Actually it is near-zero cost to use but not
zero-cost to our users who have to read it multiple places. (Think dumb
product warning labels.)
What I have done is to move the item up to the top of our
incompatibilities list in the release notes. That is near zero cost for
everyone.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2007-11-17 21:09:26 | Re: [pgsql-advocacy] Avoiding upgrade backlash |
Previous Message | Joshua D. Drake | 2007-11-17 21:01:01 | Re: [pgsql-advocacy] Avoiding upgrade backlash |
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2007-11-17 21:09:26 | Re: [pgsql-advocacy] Avoiding upgrade backlash |
Previous Message | Joshua D. Drake | 2007-11-17 21:01:01 | Re: [pgsql-advocacy] Avoiding upgrade backlash |