Skip site navigation (1) Skip section navigation (2)

pg_subtrans directory grows over 1 GB, is there a way to control it?

From: Dennis Wang <dennis_02_2002(at)hotmail(dot)com>
To: Postgresql Help <pgsql-interfaces(at)postgresql(dot)org>
Subject: pg_subtrans directory grows over 1 GB, is there a way to control it?
Date: 2008-05-16 08:58:15
Message-ID: BAY137-W50DCFFB333D7318AD4F557D6C80@phx.gbl (view raw or flat)
Thread:
Lists: pgsql-interfaces
I am using PostgreSQL database in a location recognition application, the files under postgresql/cluster is growing and over a few days it become very large as below. 
    /var/opt/postgresql/cluster/data  166015 Kilobytes  (the actual database data)
    /var/opt/postgresql/cluster/sys/pg_clog 74188 Kilobytes  (transaction commit status data)
    /var/opt/postgresql/cluster/sys/pg_subtrans   1187032 Kilobytes (transaction status data)

The pg_clog and pg_subtrans can grow when database contains more data and more queries come in. But these figures looks rather large to me because the queries goes in the database are mainly read operation rather than write one. I got a few question to ask here:
     Is there a way to control the size of pg_clog and pg_subtrans? 
     Is the file size still be normal for the database of this size (166MB for cluster/data)?
     Does the larger pg_subtrans indicate some bad transaction happens in the database?

You expertise is very appreciated.

Thanks

Dennis



_________________________________________________________________
Are you paid what you're worth? Find out: SEEK Salary Centre
http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Fninemsn%2Eseek%2Ecom%2Eau%2Fcareer%2Dresources%2Fsalary%2Dcentre%2F%3Ftracking%3Dsk%3Ahet%3Asc%3Anine%3A0%3Ahot%3Atext&_t=764565661&_r=OCT07_endtext_salary&_m=EXT

Responses

pgsql-interfaces by date

Next:From: Alvaro HerreraDate: 2008-05-16 14:39:39
Subject: Re: pg_subtrans directory grows over 1 GB, is there away to control it?
Previous:From: Dave PageDate: 2008-05-14 20:49:24
Subject: Re: [INTERFACES] Function's final statement must be a SELECT

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group