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

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
>

Hi,

Try to run a vaccum scripts in the db.

Thanks & Regards
Dilipkumar
----- Original Message -----
From: "Benjamin Krajmalnik" <kraj@illumen.com>
To: <pgsql-admin@postgresql.org>
Sent: Monday, July 31, 2006 10:04 PM
Subject: [ADMIN] PostgreSQL hanging


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
********** DISCLAIMER **********
Information contained and transmitted by this E-MAIL is proprietary to
Sify Limited and is intended for use only by the individual or entity to
which it is addressed, and may contain information that is privileged,
confidential or exempt from disclosure under applicable law. If this is a
forwarded message, the content of this E-MAIL may not have been sent with
the authority of the Company. If you are not the intended recipient, an
agent of the intended recipient or a person responsible for delivering the
information to the named recipient, you are notified that any use,
distribution, transmission, printing, copying or dissemination of this
information in any way or in any manner is strictly prohibited. If you have
received this communication in error, please delete this mail & notify us
immediately at admin@sifycorp.com


Watch the latest updates on Mumbai, with video coverage of news, events,
Bollywood, live darshan from Siddhivinayak temple and more, only on
www.mumbailive.in

Watch the hottest videos from Bollywood, Fashion, News and more only on
www.sifymax.com


---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

http://archives.postgresql.org