pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Bakken <tom.bakken@tx.usda.gov>
To: pgsql-admin@postgresql.org
Cc: 'Peter Eisentraut' <peter_e@gmx.net>
Subject: Re: Out of space
Date: Wed, 7 Apr 2004 14:23:59 -0500
Message-ID: <001401c41cd5$e0e1e950$770e9dc7@agwest.one.usda.gov> (raw)
In-Reply-To: <200404071919.46503.peter_e@gmx.net>

I'm running version 7.1.2.  I was able to drop several tables.  That cleared
up some disk space, but for some reason now, the database won't restart.
How can you determine where the problem is when you're running
/etc/rc.d/init.d/postgresql restart?  Any ideas on that would be
appreciated.

I've got database dumps so I can always start over.

Here's a listing of /var/lib/pgsql/data:
.:
total 1494316
-rw-------    1 postgres postgres        4 Jun 21  2001 PG_VERSION
drwx------    6 postgres postgres     4096 Sep 17  2003 base
drwx------    2 postgres postgres     4096 Oct 27 13:40 global
-rw-r--r--    1 root     root         7640 Jun 29  2001 h
-rw-------    1 postgres postgres     9070 Mar  2 10:56 pg_hba.conf
-rw-------    1 postgres postgres     1118 Jun 21  2001 pg_ident.conf
-rw-------    1 postgres postgres 1528627890 Apr  7 12:32 pg_log
drwx------    2 postgres postgres     4096 Apr  7 12:32 pg_xlog
-rw-------    1 postgres postgres     3137 Jun 21  2001 postgresql.conf
-rw-------    1 postgres postgres       52 Apr  7 12:32 postmaster.opts

As far as log files to delete, here are some I thought might be safe to
delete under 

./base:
total 20
drwx------    2 postgres postgres     4096 Jul 13  2001 1
drwx------    2 postgres postgres     8192 Apr  7 12:11 185174
drwx------    2 postgres postgres     4096 Jun 21  2001 18719
drwx------    2 postgres postgres     4096 Apr  7 12:11 213304

./base/1:
total 1556
-rw-------    1 postgres postgres        0 Jun 21  2001 1215
-rw-------    1 postgres postgres        0 Jun 21  2001 1216
-rw-------    1 postgres postgres     8192 Jun 21  2001 1219
-rw-------    1 postgres postgres    16384 Jul 16  2001 1247
-rw-------    1 postgres postgres    73728 Jul 13  2001 1249
-rw-------    1 postgres postgres   229376 Jun 21  2001 1255
-rw-------    1 postgres postgres    16384 Jul 16  2001 1259
-rw-------    1 postgres postgres        0 Jun 21  2001 16567
-rw-------    1 postgres postgres     8192 Jun 21  2001 16579
-rw-------    1 postgres postgres    16384 Jun 21  2001 16600
-rw-------    1 postgres postgres    73728 Jun 21  2001 16617
-rw-------    1 postgres postgres     8192 Jun 21  2001 16642
-rw-------    1 postgres postgres     8192 Jun 21  2001 16653
-rw-------    1 postgres postgres    16384 Jun 21  2001 16685
-rw-------    1 postgres postgres     8192 Jun 21  2001 16867
-rw-------    1 postgres postgres     8192 Jun 21  2001 16934
-rw-------    1 postgres postgres        0 Jun 21  2001 16948
-rw-------    1 postgres postgres     8192 Jun 21  2001 16960
-rw-------    1 postgres postgres        0 Jun 21  2001 17033
-rw-------    1 postgres postgres        0 Jun 21  2001 17045
-rw-------    1 postgres postgres     8192 Jun 21  2001 17058
.
.
.
.

I've got a couple of directories that I suspect have stale files.  One of
them:

./base/185174 contains what appears to be current information.

Thanks

Tom Bakken
Information Resource Manager
Texas USDA, Rural Development 

-----Original Message-----
From: pgsql-admin-owner@postgresql.org
[mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Peter Eisentraut
Sent: Wednesday, April 07, 2004 12:20 PM
To: Tom Bakken; pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Out of space


Tom Bakken wrote:
> I've been running a postgres for 2 or 3 years without a problem. 
> This morning my disk space for the database filled up.  I need to
> know what transaction/log files I can truncate or delete without
> compromising the system.  These files are located under
> /var/lib/pgsql/data/

The answer is normally "none" unless you have experienced crashes or 
other problems that might have left stale files lying around.  But you 
say have had no problem ...

If you have any suspicion in that direction, please show us the exact 
files you're thinking about.  A note about which PG version you are 
running would also help.


---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

               http://www.postgresql.org/docs/faqs/FAQ.html

Attachments:

Tom.Bakken@tx.usda.gov.vcf (text/x-vcard, 446B) download BEGIN:VCARD VERSION:2.1 N:Bakken;Tom FN:Tom.Bakken@tx.usda.gov ORG:Texas State Office TEL;WORK;VOICE:(254) 742-9726 TEL;WORK;FAX:(254) 742-9709 ADR;WORK;ENCODING=QUOTED-PRINTABLE:;;101 South Main=0D=0ASuite 102;Temple;TX;76502;United States of America LABEL;WORK;ENCODING=QUOTED-PRINTABLE:101 South Main=0D=0ASuite 102=0D=0ATemple, TX 76502=0D=0AUnited States of Am= erica EMAIL;PREF;INTERNET:Tom.Bakken@tx.usda.gov REV:20040301T143942Z END:VCARD

view thread (16+ messages)  latest in thread

Message-ID: <001401c41cd5$e0e1e950$770e9dc7@agwest.one.usda.gov>
Permalink:  ../001401c41cd5$e0e1e950$770e9dc7@agwest.one.usda.gov/
Also on:    postgresql.org/message-id/001401c41cd5$e0e1e950$770e9dc7@agwest.one.usda.gov

 · 

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: tom.bakken@tx.usda.gov, peter_e@gmx.net
  Subject: Re: Out of space
  In-Reply-To: <001401c41cd5$e0e1e950$770e9dc7@agwest.one.usda.gov>
  References: <200404071919.46503.peter_e@gmx.net> <001401c41cd5$e0e1e950$770e9dc7@agwest.one.usda.gov>

* 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