QUOTE:
Exactly this issue and that you have to make a 'full' dump/restore
between major release is a big minus I hear everywhere I
explain/discuss about postgres for 24/7 and big databases.
END QUOTE
Yes but how often does a major release come out? 17th Jan 2005 was the
first date of 8.0 according to the FTP site, with 8.1 out in November 2005.
If it takes a whole day to do a dump/restore, that's only one day out of
about 270 or more.
Plus in MS SQL Server, once you've moved on a version (e.g. 7 to 2000) you
can't go back - whereas in PGSQL you can just re-dump your data and revert
back to the previous version providing you're not using any features the
previous version doesn't understand - it gives much more flexibility and
more confidence in the upgrade.
Andy
-----Original Message-----
From: pgsql-admin-owner@postgresql.org
[mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Rafael Martinez
Guerrero
Sent: Tuesday, 28 March, 2006 1:09 PM
To: Jim C. Nasby
Cc: Tom Lane; Peter Eisentraut; pgsql-admin@postgresql.org; Gregory Maxwell
Subject: Re: [ADMIN] Bloated pg_shdepend_depender_index
On Fri, 2006-03-24 at 17:43, Jim C. Nasby wrote:
>
> Therein lies part of the problem: enough disk space. Now that we're
> seeing more and more use of PostgreSQL in data warehousing, it's
> becomming less safe to assume you'll have enough disk space to fix bloat
> on large tables. Plus I suspect a lot of folks wouldn't be able to
> tolerate being locked out of a table for that long (of course that
> applies to VACUUM FULL as well...)
>
Hello
Exactly this issue and that you have to make a 'full' dump/restore
between major release is a big minus I hear everywhere I explain/discuss
about postgres for 24/7 and big databases.
It would be wonderful to see a solution to these two 'problems' in the
future so postgres becomes an even better product than it is now.
--
Rafael Martinez, <r.m.guerrero@usit.uio.no>
Center for Information Technology Services
University of Oslo, Norway
PGP Public Key: http://folk.uio.no/rafael/
---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster
!DSPAM:14,4429279535041476526676!