:That's normal. 32 meg isn't really that big. How big of a partition do
:you have this database on? Your best bet is to put it on a bigger
:partition. the pg_xlog directory is gonna be at least 16 megs for most
:installations.
:
:Do you have any transactions sitting at idle keeping postgresql from
:recycling the xlogs?
:
:Normally when you run out of space it's a lack of vacuuming, but here it
:just sounds like either the partition is too small or the postgres user is
:living under a quota on that partition.
Scott -- I'm at 93% disk usage:
[postgres - DB]$ df -m .
Filesystem 1M-blocks Used Available Use% Mounted on
- 63328 55308 4803 93% /
I don't know about transactions sitting idle--like I mentioned this DB is
read-only, and there's no writes taking place. Would I still need to
worry about transactions? How can I check to see if there are any?
Re vacuuming, I haven't run vacuum for the same reason as above. This is
only a read-only DB, and I didn't think a vacuum was necessary if there's
no writes happening to the DB.
My concern is why this problem is happening now (on a read-only DB). The
DB has had nothing written to it, no new DB's have been created, and the
disk usage has stayed constant. I'm stumped as to why this problem has
started all of a sudden.
Rgs,
Zeb