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

Re: [Win32] Problem with rename()

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Peter Brant" <Peter(dot)Brant(at)wicourts(dot)gov>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: [Win32] Problem with rename()
Date: 2006-04-18 19:01:05
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugspgsql-patches
I wrote:
> "Peter Brant" <Peter(dot)Brant(at)wicourts(dot)gov> writes:
>> Does that also explain why an attempt to make a new connection just
>> hangs?

> Actually, I was just wondering about that --- seems like a bare
> connection attempt should not generate any WAL entries.  Do you have any
> nondefault actions in ~/.psqlrc or something like that?

I just repeated the hangup scenario here, and confirmed that I can still
start and stop a plain-vanilla psql session (no ~/.psqlrc, no special
per-user or per-database settings) without it hanging.  I can also do
simple read-only SELECTs.  So I'm thinking your hang must involve some
additional non-read-only actions.

[ thinks for awhile longer ... ]  No, I take that back.  Once you'd
exhausted the current pg_clog page (32K transactions), even read-only
transactions would be blocked by the need to create a new pg_clog page
(which is a WAL-logged action).  A read-only transaction never actually
makes a WAL entry, but it does still consume an XID and hence a slot on
the current pg_clog page.  So I just hadn't tried enough transactions.

			regards, tom lane

In response to


pgsql-bugs by date

Next:From: Bruce MomjianDate: 2006-04-18 22:51:43
Subject: Re: problem with kill script
Previous:From: Magnus HaganderDate: 2006-04-18 19:00:54
Subject: Re: Permission denied on fsync / Win32 (was right

pgsql-patches by date

Next:From: Bruce MomjianDate: 2006-04-19 02:50:24
Subject: Re: bug in windows xp
Previous:From: Tom LaneDate: 2006-04-18 18:44:32
Subject: Re: [Win32] Problem with rename()

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