Re: [HACKERS] MySQL vs PostgreSQL.

On Saturday 12 October 2002 09:02, Shridhar Daithankar wrote:
> On 12 Oct 2002 at 11:36, Darko Prenosil wrote:
> > On Friday 11 October 2002 12:38, Shridhar Daithankar wrote:
> > > On 11 Oct 2002 at 16:20, Antti Haapala wrote:
> > > > Check out:
> > > >   http://www.mysql.com/doc/en/MySQL-PostgreSQL_features.html
> > >
> > > Well, I guess there are many threads on this. You can dig around
> > > archives..
> > >
> > > > > Upgrading MySQL Server is painless. When you are upgrading MySQL
> > > > > Server, you don't need to dump/restore your data, as you have to do
> > > > > with most PostgreSQL upgrades.
> > > >
> > > > Ok... this is true, but not so hard - yesterday I installed 7.3b2
> > > > onto my linux box.
> > >
> > > Well, that remains as a point. Imagine a 100GB database on a 150GB disk
> > > array. How do you dump and reload? In place conversion of data is an
> > > absolute necessary feature and it's already on TODO.
> >
> > From PostgreSQL 7.3 Documentation :
> >
> > Use compressed dumps. Use your favorite compression program, for example
> > gzip. pg_dump dbname | gzip > filename.gz
>
> Yes. but that may not be enough. Strech the situation. 300GB database 350GB
> space. GZip can't compress better than 3:1. And don't think it's
> imagination. I am preparing a database of 600GB in near future. Don't want
> to provide 1TB of space to include redump.
>
Where You store Your regular backup (The one You use for security reasons, not
for version change)? Or You are not doing backup at all ???