pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Kevin Johnson <Kevin.Johnson@noaa.gov>
Cc: pgsql-admin@postgresql.org
Subject: Re: pg_subtrans
Date: Fri, 19 Feb 2010 09:40:12 -0500
Message-ID: <2640.1266590412@sss.pgh.pa.us> (raw)
In-Reply-To: <4B7EA146.5060501@noaa.gov>
References: <4B7EA146.5060501@noaa.gov>

Kevin Johnson <Kevin.Johnson@noaa.gov> writes:
> I am attempting to get information on the pg_subtrans directory.  I 
> found this morning that one had a large number of files queued in it.  
> It filled the disk partition on which pgdata resides.  After moving, 
> linking and restarting as a temporary solution, the engine properly 
> worked off these files.  So, I'm trying now to get to the root cause of 
> why it filled in the first place -- however I'm not sure when postgres 
> engine uses this directory.  I've searched the documentation and mailing 
> list archive, but can't find much.  Can anyone give me a link or some 
> more information?

I don't recall the exact horizon for pg_subtrans offhand, but I'm pretty
sure that it's determined by your oldest open transaction.  Look around
for idle-in-transaction sessions.

			regards, tom lane



view thread (2+ messages)

Message-ID: <2640.1266590412@sss.pgh.pa.us>
Permalink:  ../2640.1266590412@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/2640.1266590412@sss.pgh.pa.us

 · 

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 using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: tgl@sss.pgh.pa.us, Kevin.Johnson@noaa.gov
  Subject: Re: pg_subtrans
  In-Reply-To: <2640.1266590412@sss.pgh.pa.us>

* 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