From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | Lamar Owen <lowen(at)pari(dot)edu> |
Cc: | Dennis Gearon <gearond(at)fireserve(dot)net>, Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net>, PgSQL General ML <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: State of Beta 2 |
Date: | 2003-09-15 18:24:43 |
Message-ID: | 3F6603EB.3000409@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> Strawmen. If we provide a good upgrade capability, we would just
> simply have to think about upgrades before changing features like
> that. The upgrade code could be cognizant of these sorts of things;
> and shoud be, in fact.
Sure but IMHO it would be more important to fix bugs like the parser not
correctly using indexes on bigint unless the value is quoted...
I think everyone would agree that not having to use initdb would be nice
but I think there is much more important things to focus on.
Besides if you are upgrading PostgreSQL in a production environment I
would assume there would be an extremely valid reason. If the reason is
big enough to do a major version upgrade then an initdb shouldn't be all
that bad of a requirement.
J
--
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-222-2783 - jd(at)commandprompt(dot)com - http://www.commandprompt.com
The most reliable support for the most reliable Open Source database.
From | Date | Subject | |
---|---|---|---|
Next Message | Holger Marzen | 2003-09-15 18:36:34 | Re: pg 7.3.4 and linux box crash |
Previous Message | Abdul-Wahid Paterson | 2003-09-15 18:18:07 | after postgres upgrade - ERROR: current transaction is aborted |