pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Warren Snelling <snelling@email.marc.usda.gov>
To: gbarosio@gmail.com
Cc: pgsql-admin@postgresql.org
Subject: Re: 7.4 <-> 8.0
Date: Fri, 16 Sep 2005 10:57:16 -0500
Message-ID: <1126886236.12350.106.camel@localhost> (raw)
In-Reply-To: <f7f6b4c705091513473b7def79@mail.gmail.com>
References: <1126811405.12350.29.camel@localhost>
	<f7f6b4c7050915133528861ce5@mail.gmail.com>
	<f7f6b4c705091513473b7def79@mail.gmail.com>

Guido,

Thanks for the pointers.  I have routinely vacuumed the db, but not
using full. 

By itself, the "vacuum full" run overnight did not free the space I was
expecting - du still showed the old database taking about 12 Gb disk,
and the fresh databases taking about 6.5 Gb.  Running "reindex" on one
large table freed ~5 Gb, so the old db now takes 7 Gb.  Reindexing the
remaining tables should get the databases to the same size.

Would you suggest scripting the vacuum full / reindex process to run
periodically (once a week or so)?  Right now disk space on this machine
is not an issue, but vacuuming and reindexing occasionally should keep
the db from consuming too much excess space.

Thanks again,
warren

> still thinking on this topic, read about the REINDEX command, that
> will recreate your indexes, per table or per database.
>  
> Regards,
> Guido.
> 
>  
> On 9/15/05, Guido Barosio <gbarosio@gmail.com> wrote: 
>         Hi Warren
>          
>         On the space issue, seems at a first sight that the old db
>         needs a vacuum full to free some room.
>         Try to identify your biggest tables, isolate the vacuum
>         against them, and then escalate to the whole db, with a vacuum
>         full.
>          
>         Thinking that you should double check the vacuum
>         documentation, to understand better which are the effects of
>         the different vacuum modes. This will clear out your doubts on
>         why such amount of space is being allocated, but not being
>         used. 
>          
>         My two cents there.
>          
>         Best wishes,
>         Guido.
>          
>         On 9/15/05, Warren Snelling <snelling@email.marc.usda.gov>
>         wrote: 
>                 All,
>                 
>                 Couple questions from to a recent upgrade from 7.4.8
>                 to 8.0.3.  With
>                 servers for both versions running on the same
>                 machine, 
>                 
>                   pg_dumpall -p 5432 -c | psql -p 5433 template1
>                 
>                 appears to have migrated the databases smoothly.  At
>                 least I didn't
>                 notice any errors in the process, and all the data
>                 appears to be there.
>                 
>                 The one troubling thing is the new 8.0 databases take
>                 about half the
>                 disk space as the 7.4 databases.  Similar dump | psql
>                 to recreate the
>                 databases on other machines running 7.4.7 and 7.4.8
>                 show the same thing
>                 - the fresh copies take half the space of the
>                 old.  What might be 
>                 happening with the old db, so it takes so much more
>                 space?  Could half
>                 the data be missing?
>                 
>                 What's the best way to move data from 8.0 to 7.4?  The
>                 8.0 pg_dump
>                 writes a dump that doesn't restore with 7.4 psql, and
>                 7.4 pg_dump
>                 doesn't seem to handle an 8.0 database.  At least I
>                 haven't found the
>                 right switches...
>                 
>                 Thanks,
>                 warren
>                 
>                 
>                 ---------------------------(end of
>                 broadcast)---------------------------
>                 TIP 2: Don't 'kill -9' the postmaster 
>         
>         
>         
>         
>         -- 
>         "Adopting the position that you are smarter than an automatic
>         optimization algorithm is generally a good way to achieve less
>         performance, not more" - Tom Lane. 
> 
> 
> 
> -- 
> "Adopting the position that you are smarter than an automatic
> optimization algorithm is generally a good way to achieve less
> performance, not more" - Tom Lane. 




view thread (7+ messages)  latest in thread

Message-ID: <1126886236.12350.106.camel@localhost>
Permalink:  ../1126886236.12350.106.camel@localhost/
Also on:    postgresql.org/message-id/1126886236.12350.106.camel@localhost

 · 

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: snelling@email.marc.usda.gov, gbarosio@gmail.com
  Subject: Re: 7.4 <-> 8.0
  In-Reply-To: <1126886236.12350.106.camel@localhost>
  References: <1126811405.12350.29.camel@localhost> <f7f6b4c7050915133528861ce5@mail.gmail.com> <f7f6b4c705091513473b7def79@mail.gmail.com> <1126886236.12350.106.camel@localhost>

* 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