When I started this thread I made comment on the fact that this initdb
issue was treated somewhat "casually" on the lists. Not trying to
flame, or be an ass or anything, but this is kind of what I meant.
Yes, I know there many important issues the developers (bless their
overworked fingers) want/need to address that affect many people, and
I'm not going to presume to fault their choices. Some things make more
difference to others (the bigint indexing issue means little to me, for
example), so we try to point out these things in the hope that someone
may pick up on it, or the discussion may bear fruitful solutions that
no one had considered.
The initdb situation is a significant problem/obstacle to many people.
Avoiding it would be far more than 'nice' for us.
On Monday, September 15, 2003, at 02:24 PM, Joshua D. Drake wrote:
>
>> 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@commandprompt.com - http://www.commandprompt.com
> The most reliable support for the most reliable Open Source database.
>
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
>
--------------------
Andrew Rawnsley
President
The Ravensfield Digital Resource Group, Ltd.
(740) 587-0114
www.ravensfield.com