Re: Why dump/restore to upgrade? - Mailing list pgsql-hackers

From Matthew T. O'Connor
Subject Re: Why dump/restore to upgrade?
Date
Msg-id 200202081615.g18GFWG13980@neuromancer.ctlno.com
Whole thread Raw
In response to Re: Why dump/restore to upgrade?  (mlw <markw@mohawksoft.com>)
List pgsql-hackers
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> I don't want to say "Other databases do it, why can't PostgreSQL" because
> that isn't the point. Databases can be HUGE, pg_dumpall can take an hour or
> more to run. Then, it takes longer to restore because indexes have to be
> recreated.

A way to put PostgreSQL into a read only mode could help this (as well as 
many other things.)  That way they could at least let users have access to 
the data the entire time that the dump restore process is going.  It could 
take a lot of disk space, but it would help the case where time is a bigger 
problem than space.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8Y/oc8BXvT14W9HARAiGgAJ9ckgaq2YHupc/1Wl6RlRNJ5UulNwCeNWrt
ZrVN4qo+L9nDckpIPQ80MYM=
=1WXQ
-----END PGP SIGNATURE-----


pgsql-hackers by date:

Previous
From: hiroyuki hanai
Date:
Subject: Re: compile error of PostgreSQL 7.2 on FreeBSD-current
Next
From: Tom Lane
Date:
Subject: Re: Threaded PosgreSQL server