Re: [pgsql-advocacy] Avoiding upgrade backlash
От | Bruce Momjian |
---|---|
Тема | Re: [pgsql-advocacy] Avoiding upgrade backlash |
Дата | |
Msg-id | 200711172105.lAHL5oV02191@momjian.us обсуждение исходный текст |
Ответ на | Re: [pgsql-advocacy] Avoiding upgrade backlash ("Joshua D. Drake" <jd@commandprompt.com>) |
Ответы |
Re: [pgsql-advocacy] Avoiding upgrade backlash
Re: [pgsql-advocacy] Avoiding upgrade backlash |
Список | pgsql-docs |
Joshua D. Drake wrote: > Tom Lane wrote: > > "Joshua D. Drake" <jd@commandprompt.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@momjian.us> http://momjian.us EnterpriseDB http://postgres.enterprisedb.com + If your life is a hard drive, Christ can be your backup. +
В списке pgsql-docs по дате отправления: