Re: Release cycle length
От | Alvaro Herrera |
---|---|
Тема | Re: Release cycle length |
Дата | |
Msg-id | 20031121130359.GE26392@dcc.uchile.cl обсуждение исходный текст |
Ответ на | Re: Release cycle length (Christopher Kings-Lynne <chriskl@familyhealth.com.au>) |
Ответы |
Re: Release cycle length
|
Список | pgsql-hackers |
On Fri, Nov 21, 2003 at 09:38:50AM +0800, Christopher Kings-Lynne wrote: > >Yeah, I think the main issue in all this is that for real production > >sites, upgrading Postgres across major releases is *painful*. We have > >to find a solution to that before it makes sense to speed up the > >major-release cycle. > > Well, I think one of the simplest is to do a topological sort of objects > in pg_dump (between object classes that need it), AND regression > testing for pg_dump :) One of the most complex would be to avoid the need of pg_dump for upgrades ... -- Alvaro Herrera (<alvherre[@]dcc.uchile.cl>) "I call it GNU/Linux. Except the GNU/ is silent." (Ben Reiter)
В списке pgsql-hackers по дате отправления: