From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | Dan Langille <dan(at)langille(dot)org>, Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> |
Cc: | Merlin Moncure <merlin(dot)moncure(at)rcsonline(dot)com>, LSanchez(at)ameritrade(dot)com, pgsql-advocacy(at)postgresql(dot)org |
Subject: | Re: PostgreSQL vs MySQL |
Date: | 2004-05-20 20:27:33 |
Message-ID: | 200405201327.33678.josh@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy |
Dan, Robert
> This is an issue frequently raised with Bacula (http://www.bacula.org/)
> How do I backup my 20GB database if I have only 1GB free diskspace?
> Bacula can use a FIFO, although I've never used it myself.
My answer to this would be "stop being such a cheapskate and spend $150 on
another HDD, darn it!"
> and the like, with varying degrees of success. Between that and really
> big disks/raid setups you can get pretty far, certainly into the triple
> digit GB range. Beyond that I'm not quite sure how people handle TB
> sized databases, but those folks are out there so it must be doable.
As someone who admins some of these large databases, right now it's a PITA.
I'm constantly trying to get my clients to chip in to fund development of
table partitioning -- we could really use it.
Mostly, right now, we make do with huge SANs. But it's a problem for the
clients whose data is growing but don't have $35,000 to spend on a
high-quality SAN.
On the otherhand, if one of my clients told me they wanted to load 500GB of
data into a MySQL database, I'd tell them "Nice knowing you!". Total
suicide -- you wouldn't be able to back it up, for one thing. Let alone
trying to manage disk I/O -- forget it.
--
-Josh Berkus
Aglio Database Solutions
San Francisco
From | Date | Subject | |
---|---|---|---|
Next Message | LSanchez | 2004-05-20 21:42:54 | pgSQL deployment |
Previous Message | Dan Langille | 2004-05-20 20:08:28 | Re: PostgreSQL vs MySQL |