Re: Re: [GENERAL] PostgreSQL vs. MySQL

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu>, Philip Warner <pjw(at)rhyme(dot)com(dot)au>, Chris Bitmead <chrisb(at)nimrod(dot)itg(dot)telstra(dot)com(dot)au>, "pgsql-hackers(at)postgreSQL(dot)org" <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: Re: [GENERAL] PostgreSQL vs. MySQL
Date: 2000-07-10 21:38:38
Message-ID: 200007102138.RAA03774@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

> I'm not by any means sold on removing the physical separation between
> databases --- I can see lots of reasons not to. But I think we ought
> to think hard about the choice, not have a knee-jerk reaction that we
> don't want to "eliminate a feature". Physically separate databases
> are an implementation choice, not a user feature.

If we put tables from different database in the same tablespace
directory, and a database gets hosed, there is no way to delete the
files associated with the hosed database, unless we go around and find
all the table files used by all databases, then remove the ones not
referenced.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Browse pgsql-general by date

  From Date Subject
Next Message David C Mudie 2000-07-10 22:15:26 pgsql gives ExecutePlan error after empty UPDATE?
Previous Message Bruce Momjian 2000-07-10 21:32:35 Re: Re: [SQL] Re: [GENERAL] lztext and compression ratios...

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2000-07-10 22:03:30 Re: libpq work
Previous Message Bruce Momjian 2000-07-10 21:32:35 Re: Re: [SQL] Re: [GENERAL] lztext and compression ratios...