From: | Kaare Rasmussen <kar(at)kakidata(dot)dk> |
---|---|
To: | PgSQL General ML <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: State of Beta 2 |
Date: | 2003-09-17 08:45:36 |
Message-ID: | 200309171045.36455.kar@kakidata.dk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
>> If someone is willing to pony up 2000.00 per month for a period of at
>> least 6 months, I will dedicated one of my programmers to the task.
I stated the "how much will it cost" question, but I'm beginning to think that
it's the wrong approach. From the answers in this thread I do believe that it
will be an eternal chase with almost certainty of errors.
Some people have claimed that the big commercial databases don't change their
on-disk represantation anymore. Maybe PostgreSQL could try to aim for this
goal. At least try to get the on-disk changes ready for 7.5 - with or without
the functionality to use it. I think that any pg_* table changes could be
done with a small and efficient pg_upgrade.
Big items that will change the way PostgreSQL stores its data would be
Tablespaces
PITR
...
More ?
I know it's not possible to tell the future, but if Oracle is steady,
shouldn't it be possible?
How do other Open Source systems do ? MySQL (or maybe better: InnoDB),
FireBird ??
--
Kaare Rasmussen --Linux, spil,-- Tlf: 3816 2582
Kaki Data tshirts, merchandize Fax: 3816 2501
Howitzvej 75 Åben 12.00-18.00 Email: kar(at)kakidata(dot)dk
2000 Frederiksberg Lørdag 12.00-16.00 Web: www.suse.dk
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua Moore-Oliva | 2003-09-17 08:46:11 | Problems requiring a GROUP BY clause on update? |
Previous Message | Mark Cave-Ayland | 2003-09-17 08:13:10 | Re: State of Beta 2 |