Re: device full ---> postgres will not start

i will take the advice and upgrade to 7.2.4 ASAP as in now.

this what rpm reports on the server currently:
[root(at)localhost root]# rpm -qa | grep postgres
postgresql-jdbc-7.2.1-5
postgresql-libs-7.2.1-5
postgresql-7.2.1-5
postgresql-server-7.2.1-5
postgresql-contrib-7.2.1-5
postgresql-devel-7.2.1-5
[root(at)localhost root]#

i downloaded the following:
[root(at)localhost download]# ls
postgresql-7.2.4-1PGDG.i386.rpm postgresql-libs-7.2.4-1PGDG.i386.rpm
postgresql-contrib-7.2.4-1PGDG.i386.rpm postgresql-perl-7.2.4-1PGDG.i386.rpm
postgresql-devel-7.2.4-1PGDG.i386.rpm postgresql-server-7.2.4-1PGDG.i386.rpm
postgresql-docs-7.2.4-1PGDG.i386.rpm postgresql-tcl-7.2.4-1PGDG.i386.rpm
postgresql-jdbc-7.2.4-1PGDG.i386.rpm
[root(at)localhost download]#

i have done new installs using RPMs, but not an upgrade.
silly question time:
are these the correct RPMs?
do I just upgrade them one at a time as follows:
rpm -Uvh postgresql.......rpm

many thanks

kd

scott(dot)marlowe(at)ihs(dot)com ("scott.marlowe") wrote in message news:<Pine(dot)LNX(dot)4(dot)33(dot)0310270756530(dot)14845-100000(at)css120(dot)ihs(dot)com>...
> On Fri, 24 Oct 2003, Duffy House wrote:
>
> > Hello:
> >
> > It looks like I got caught sleeping.
> >
> > I am running Postgresql 7.2 under Red Hat 7.3.
> > Postgresql failed today. When I tried to restart it, I got a message
> > stating that the device is full.
> > I used df to confirm that /var where postgres reside is full. /var is on a
> > 4 Gig device.
> > Postgresql is the only application on this machine.
> >
> > Please note, the backup of the database from the prior day, is 45 Meg
> > zipped.
> > I do not know how the database could be soaking up a 4 Gig device.
> >
> > Questions:
> >
> > How can I recover from this situation?
> >
> > If postgres will not start how can I restore the database from the prior
> > day?
> >
> > When I run a backup does postgres truncate its logs?
> >
> > please keep it simple, I have about 1 hours admin experience with postgres.
> >
> > thanks in advance.
>
> It sounds like either you've never run vacuum, or you've had a few threads
> holding transactions open for a very long time.
>
> Easiest way to recover: Make a bigger partition, cp everything there, and
> point the postmaster at that partition to startup. Then vacuum etc... and
> copy it all back over the original partition. Then make sure you're
> running the latest and greatest (at least 7.2.4, prefereable 7.3.4) and
> look up the autovacuum daemon to make sure this never happens again. If
> you installed from source, it's in the contrib/pg_autovacuum directory,
> just cd in there as root, and 'make;make install' and it's installed.
>
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly