From: Rafael Martinez <r.m.guerrero@usit.uio.no>
To: Scott Marlowe <smarlowe@g2switchworks.com>
Cc: Jim C. Nasby <jnasby@pervasive.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Bloated pg_shdepend_depender_index
Date: Wed, 29 Mar 2006 01:05:59 +0200
Message-ID: <1143587159.18329.56.camel@linux.site> (raw)
In-Reply-To: <1143580500.3625.92.camel@state.g2switchworks.com>
References: <1143547721.24060.112.camel@bbking.uio.no>
<!&!AAAAAAAAAAAuAAAAAAAAALfqleqaijxJlxu+E5RYF+YBAJaQ0jfg6zBFp7poaER6UCkAAAGy3PcAABAAAABwyDMRZahASK/KqNE2uIW9AQAAAAA=@mailnetwork.co.uk>
<20060328180937.GS75181@pervasive.com>
<1143575509.18329.13.camel@linux.site>
<1143580500.3625.92.camel@state.g2switchworks.com>
On Tue, 2006-03-28 at 15:15 -0600, Scott Marlowe wrote:
> On Tue, 2006-03-28 at 13:51, Rafael Martinez wrote:
> > On Tue, 2006-03-28 at 12:09 -0600, Jim C. Nasby wrote:
> >
> > >
> > > Fortunately, you can use Slony to migrate between versions, greatly
> > > reducing downtime.
> >
> > Yes, this is true, but the problem is that if the database is 'big' and
> > running in an expensive system you need to double your investment only
> > for the upgrade.
> >
> > I am sure we can find another way of doing this that is easier and
> > faster.
>
> Any large, production system should already have replication in place.
>
> If not, you're taking your chances with that big system that make any
> investment questionable. If downtime is a real problem.
You do not need replication in place to run a large system in a
responsible way. I agree that you need redundance in many layers but you
have to stop at some point.
We have for example, some big/expensive disk arrays in our system that
have a lot of redundancy, redundant hot plug power supplies, redundant
hot plug blowers, redundant hot plug cache batteries, redundant hot plug
FC I/O modules, redundant pair of controllers, etc, etc and an expensive
24x7 onsite hardware support. But we do not have an extra disk array
just in case the one in production stops working (it can happen but we
have to trust it won't)
Fast scsi disks in this type of array are not cheap, and the bosses are
not happy if you say that you need the double of space to upgrade the
system, this can be very expensive in a big system.
I work with postgresql every day and I am very happy with it, but this
does not mean I can not see the issues that could be improve to have a
even better open source DBMS. And I think in my humble opinion that
bloated indexes + better upgrade procedures between major releases are
two things that should get improved in the future.
regards,
--
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/
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: r.m.guerrero@usit.uio.no, smarlowe@g2switchworks.com, jnasby@pervasive.com
Subject: Re: Bloated pg_shdepend_depender_index
In-Reply-To: <1143587159.18329.56.camel@linux.site>
References: <1143547721.24060.112.camel@bbking.uio.no> <!&!AAAAAAAAAAAuAAAAAAAAALfqleqaijxJlxu+E5RYF+YBAJaQ0jfg6zBFp7poaER6UCkAAAGy3PcAABAAAABwyDMRZahASK/KqNE2uIW9AQAAAAA=@mailnetwork.co.uk> <20060328180937.GS75181@pervasive.com> <1143575509.18329.13.camel@linux.site> <1143580500.3625.92.camel@state.g2switchworks.com> <1143587159.18329.56.camel@linux.site>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox