| From: | Dan Langille <dan(at)langille(dot)org> |
|---|---|
| To: | 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:08:28 |
| Message-ID: | 20040520160705.R64060@xeon.unixathome.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy |
On Thu, 20 May 2004, Robert Treat wrote:
> One potential issue with PostgreSQL and big databases would be
> upgrades and backups, which require dumping lots of data to disk which
> can be inconvenient. If I were a big company looking to switch to
> postgresql, I'd think hard about using some of the money I saved in
> license fee's to get in place upgrades developed.
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.
--
Dan Langille - BSDCan: http://www.bsdcan.org/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2004-05-20 20:27:33 | Re: PostgreSQL vs MySQL |
| Previous Message | Robert Treat | 2004-05-20 20:00:52 | Re: PostgreSQL vs MySQL |