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: Fri, 31 Mar 2006 12:37:32 -0600
Message-ID: <20060331183732.GV49405@pervasive.com> (raw)
In-Reply-To: <1143652750.18329.89.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>
	<20060328231707.GA561@pervasive.com>
	<1143652750.18329.89.camel@linux.site>

On Wed, Mar 29, 2006 at 07:19:10PM +0200, Rafael Martinez wrote:
> On Tue, 2006-03-28 at 17:17 -0600, Jim C. Nasby wrote:
> > 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. 
> 
> I know there is not an easy solution to the dump/restore procedure, and
> maybe even it is not possible (I am not a postgres developer and don't
> know the postgres internals and what it is necessary to do between major
> releases) Does the file structures change always between every major
> release?

It depends. Sometimes the changes aren't as much in the files as they
are in the system catalogs.

Ideally, what we'd have is the ability to deal with data that was stored
in the last versions format. Any time an old row gets changed, it gets
re-written in the new format (probably on a different page). While this
would present some challenges, it would make for very, very fast
upgrades.

Unfortunately, it would also greatly increase code complexity and
maintenance costs, so it's rather unlikely it will ever happen. Maybe if
someone forks over a very large sum of money, but even then it's
unlikely...

An actual upgrade script is more likely, but even there you still need
to have a backup (actually, that's really pretty true of both cases).
This idea does have some traction though, and if someone produced a
working utility there's a decent chance it would be accepted.
-- 
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: <20060331183732.GV49405@pervasive.com>
Permalink:  ../20060331183732.GV49405@pervasive.com/
Also on:    postgresql.org/message-id/20060331183732.GV49405@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: <20060331183732.GV49405@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> <1143652750.18329.89.camel@linux.site> <20060331183732.GV49405@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