> Before I do that I want to confirm the major problem I had w/postgres:
> the 8K tuple limit. When trying to import some tables from MySQL,
> postgres kept choking because MySQL has no such limit on the size of a
> row in the database (text fields on MySQL can be multi-megabyte).
Jan is working on TOAST for 7.1 - there will be no 8K limit any more...
> Long-term stability:
> Postgres is undoubtably the long-run winner in stability,
> whereas MySQL will freak out or die when left running for more than a
> at a time. But if you ever do have a problem with postgres, you generally
> have to nuke the database and recover from a backup, as there are no
> known tools to fix index and database corruption. For a long-running
> database, you will occasionally have to drop indexes and re-create them,
> causing downtime.
I'm implementing WAL for 7.1 - there will be true after crash recovery...
pgsql-hackers by date
|Next:||From: Egon Schmid||Date: 2000-07-04 19:51:11|
|Subject: Re: Article on MySQL vs. Postgres|
|Previous:||From: Tim Perdue||Date: 2000-07-04 19:42:31|
|Subject: Article on MySQL vs. Postgres|