pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jim C. Nasby <jnasby@pervasive.com>
To: Rafael Martinez <r.m.guerrero@usit.uio.no>
Cc: Scott Marlowe <smarlowe@g2switchworks.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Bloated pg_shdepend_depender_index
Date: Tue, 28 Mar 2006 17:17:08 -0600
Message-ID: <20060328231707.GA561@pervasive.com> (raw)
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>

On Wed, Mar 29, 2006 at 01:05:59AM +0200, Rafael Martinez wrote:
> 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. 

FWIW, I don't know of any upgrade procedures for databases that can
quickly do an in-place upgrade when underlying file structures change,
because ultimately you need to read and write the entire database
on-disk. And unless you're going to be real gutsy, you'll also need a
good amount of extra storage somewhere, unless you plan on doing this
in-place upgrade without any backups. And at that point, you almost
might as well just do a dump and reload.

Given that, I don't think setting up a temporary Slony cluster to go
between major versions is that big a deal.
-- 
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461



view thread (26+ messages)  latest in thread

Message-ID: <20060328231707.GA561@pervasive.com>
Permalink:  ../20060328231707.GA561@pervasive.com/
Also on:    postgresql.org/message-id/20060328231707.GA561@pervasive.com

 · 

reply

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: jnasby@pervasive.com, r.m.guerrero@usit.uio.no, smarlowe@g2switchworks.com
  Subject: Re: Bloated pg_shdepend_depender_index
  In-Reply-To: <20060328231707.GA561@pervasive.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> <1143587159.18329.56.camel@linux.site> <20060328231707.GA561@pervasive.com>

* 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