X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 2F7539FB319 for ; Mon, 31 Jul 2006 14:58:00 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 12839-09 for ; Mon, 31 Jul 2006 14:57:56 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.176]) by postgresql.org (Postfix) with ESMTP id 9D8C89FB307 for ; Mon, 31 Jul 2006 14:57:55 -0300 (ADT) Received: by py-out-1112.google.com with SMTP id b36so583708pyb for ; Mon, 31 Jul 2006 10:57:53 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=M+/8Sa9DMEc2m1qMHPwMTQOYoeArQo7ULTSpBvbFoh1ZgFm6i+KUq988Kb6T9owrMMCEBKikUnfpM3Px50eTikg7j6AwokAOHnvKA0/lSfab73Xv95cztcYebd07BkxTrxTpz4Ys5QbndaAjk91+9FQbyBSXgfuhid30RjDbR2A= Received: by 10.35.60.16 with SMTP id n16mr4228539pyk; Mon, 31 Jul 2006 10:57:53 -0700 (PDT) Received: by 10.35.61.12 with HTTP; Mon, 31 Jul 2006 10:57:53 -0700 (PDT) Message-ID: Date: Mon, 31 Jul 2006 22:57:53 +0500 From: "Shoaib Mir" To: "Benjamin Krajmalnik" Subject: Re: PostgreSQL hanging Cc: pgsql-admin@postgresql.org In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_61933_32206925.1154368673624" References: X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.44 tagged_above=0 required=5 tests=AWL, DNS_FROM_RFC_ABUSE, HTML_50_60, HTML_MESSAGE, SPF_PASS X-Spam-Level: X-Archive-Number: 200607/295 X-Sequence-Number: 22541 ------=_Part_61933_32206925.1154368673624 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Do you have any antivirus running on your system? if so, try disabling that. This problem can occur if some other process is holding a lock on that specific file and so as a result not able to rename the file. Thanks, -- Shoaib Mir EnterpriseDB (www.enterprisedb.com) On 7/31/06, Benjamin Krajmalnik wrote: > > I am runing PG 8.1.4/Windows. > Over the weekend, I have had to restart the PostgreSQL service a couple > of times after PG hangs. > At the time this happens, the log is showing entries such as the one > below > > 2006-07-31 09:19:55 LOG: could not rename file > "pg_xlog/0000000100000208000000E1" to > "pg_xlog/0000000100000208000000F4", continuing to try > > Any ideas what may be causing this? > > My database is currently 7.7 GB. > I have 54GB of drive space available, so it is not being caused by lack > of disk space. > > My autovacuum parameters are as follows: > > #----------------------------------------------------------------------- > ---- > # AUTOVACUUM PARAMETERS > #----------------------------------------------------------------------- > ---- > > autovacuum = on # enable autovacuum subprocess? > autovacuum_naptime = 20 # time between autovacuum runs, in secs > autovacuum_vacuum_threshold = 100 # min # of tuple updates before > # vacuum > autovacuum_analyze_threshold = 100 # min # of tuple updates before > # analyze > autovacuum_vacuum_scale_factor = 0.1 # fraction of rel size before > # vacuum > autovacuum_analyze_scale_factor = 0.1 # fraction of rel size before > # analyze > autovacuum_vacuum_cost_delay = 100 # default vacuum cost delay for > # autovac, -1 means use > # vacuum_cost_delay > autovacuum_vacuum_cost_limit = 100 # default vacuum cost limit for > # autovac, -1 means use > # vacuum_cost_limit > > > Any suggestions will be appreciated. > > ---------------------------(end of broadcast)--------------------------- > TIP 6: explain analyze is your friend > ------=_Part_61933_32206925.1154368673624 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Do you have any antivirus running on your system? if so, try disabling that.

This problem can occur if some other process is holding a lock on that specific file and so as a result not able to rename the file.

Thanks,
--
Shoaib Mir
EnterpriseDB (www.enterprisedb.com)

On 7/31/06, Benjamin Krajmalnik < kraj@illumen.com> wrote:
I am runing PG 8.1.4/Windows.
Over the weekend, I have had to restart the PostgreSQL service a couple
of times after PG hangs.
At the time this happens, the log is showing entries such as the one
below

2006-07-31 09:19:55 LOG:  could not rename file
"pg_xlog/0000000100000208000000E1" to
"pg_xlog/0000000100000208000000F4", continuing to try

Any ideas what may be causing this?

My database is currently 7.7 GB.
I have 54GB of drive space available, so it is not being caused by lack
of disk space.

My autovacuum parameters are as follows:

#-----------------------------------------------------------------------
----
# AUTOVACUUM PARAMETERS
#-----------------------------------------------------------------------
----

autovacuum = on                 # enable autovacuum subprocess?
autovacuum_naptime = 20         # time between autovacuum runs, in secs
autovacuum_vacuum_threshold = 100       # min # of tuple updates before
                                        # vacuum
autovacuum_analyze_threshold = 100      # min # of tuple updates before
                                        # analyze
autovacuum_vacuum_scale_factor = 0.1    # fraction of rel size before
                                        # vacuum
autovacuum_analyze_scale_factor = 0.1   # fraction of rel size before
                                        # analyze
autovacuum_vacuum_cost_delay = 100      # default vacuum cost delay for
                                        # autovac, -1 means use
                                        # vacuum_cost_delay
autovacuum_vacuum_cost_limit = 100      # default vacuum cost limit for
                                        # autovac, -1 means use
                                        # vacuum_cost_limit


Any suggestions will be appreciated.

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend




------=_Part_61933_32206925.1154368673624--