Re: [HACKERS] Postmaster holding unlinked files for pg_largeobject table

From: Jeff Davis <pgsql(at)j-davis(dot)com>
To: Alexander Shulgin <ash(at)commandprompt(dot)com>
Cc: pgsql-general(at)postgresql(dot)org, alexk <alexk(at)commandprompt(dot)com>
Subject: Re: [HACKERS] Postmaster holding unlinked files for pg_largeobject table
Date: 2011-06-03 22:24:28
Message-ID: 1307139868.3398.3.camel@jdavis-ux.asterdata.local
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

[ For future reference, -general is the appropriate list. Moving
discussion there. ]

On Sat, 2011-06-04 at 00:45 +0300, Alexander Shulgin wrote:
> We've noticed that free disk space went down heavily on a system, and
> after a short analysis determined that the reason was that postmaster
> was holding lots of unlinked files open. A sample of lsof output was
> something like this:

...

> Restarting PostgreSQL obviously helps the issue and the disk space
> occupied by those unlinked files (about 63GB actually) is reclaimed.

Normally postgres closes unlinked files during a checkpoint. How long
between checkpoints on this system? Is it possible that you noticed
before postgresql caused an automatic checkpoint?

Also, you can do a manual checkpoint with the CHECKPOINT command.

Regards,
Jeff Davis

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Oliver Jowett 2011-06-03 22:39:26 Re: [GENERAL] Mixed up protocol packets in server response?
Previous Message Esmin Gracic 2011-06-03 22:09:29 Re: Need suggestion

Browse pgsql-hackers by date

  From Date Subject
Next Message Noah Misch 2011-06-03 22:27:08 Assert failure when rechecking an exclusion constraint
Previous Message Andrew Chernow 2011-06-03 22:22:06 Re: Error in PQsetvalue