Re: fsync and semctl errors with 8.1.5/win32

From: "Jeremy Haile" <jhaile(at)fastmail(dot)fm>
To: "Jeremy Haile" <jhaile(at)fastmail(dot)fm>, "Thomas H(dot)" <me(at)alternize(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Dave Page" <dpage(at)postgresql(dot)org>, "Magnus Hagander" <mha(at)sollentuna(dot)net>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: fsync and semctl errors with 8.1.5/win32
Date: 2006-11-30 14:09:46
Message-ID: 1164895786.15579.278200205@webmail.messagingengine.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Last night I received another filesystem-related problem. Shortly after
this problem occurred, I had a connection hang indefinitely, causing my
software to go down all night.

The log output that occurred shortly before the problem is below. After
that, there was no log output by PostgreSQL until I came in this morning
and killed the offending process. Any ideas? Could the pg_xlog error
below possibly result in a transaction hanging indefinitely? If so,
would the solution Tom proposed possibly fix the error?

Any update on getting a patched exe for Thomas and I to test?

2006-11-29 20:11:35 ERROR: tuple concurrently updated
2006-11-29 20:11:35 ERROR: tuple concurrently updated
2006-11-29 20:11:35 ERROR: tuple concurrently updated
2006-11-29 20:11:36 LOG: transaction ID wrap limit is 1090292093,
limited by database "incommDashboard"
2006-11-29 20:11:36 LOG: transaction ID wrap limit is 1090292093,
limited by database "incommDashboard"
2006-11-29 21:21:38 LOG: transaction ID wrap limit is 1090522044,
limited by database "incommDashboard"
2006-11-29 21:21:38 LOG: transaction ID wrap limit is 1090522044,
limited by database "incommDashboard"
2006-11-29 22:22:52 LOG: transaction ID wrap limit is 1090579373,
limited by database "incommDashboard"
2006-11-29 22:22:52 LOG: transaction ID wrap limit is 1090579373,
limited by database "incommDashboard"
2006-11-29 23:38:47 LOG: transaction ID wrap limit is 1090633937,
limited by database "incommDashboard"
2006-11-29 23:38:47 LOG: transaction ID wrap limit is 1090633937,
limited by database "incommDashboard"
2006-11-29 23:57:52 LOG: could not rename file
"pg_xlog/00000001000000190000005E" to
"pg_xlog/00000001000000190000007F", continuing to try

On Tue, 28 Nov 2006 17:49:22 -0500, "Jeremy Haile" <jhaile(at)fastmail(dot)fm>
said:
> I am currently running 8.1.5, but I'm willing to upgrade to whatever
> version, use a patched exe, etc. Just let me know what I need to do.
>
> On Tue, 28 Nov 2006 23:39:00 +0100, "Thomas H." <me(at)alternize(dot)com> said:
> > > Perhaps this should be #ifdef WIN32, although there's probably no harm
> > > in doing it on Unixen too. Can someone test this idea?
> >
> > if magnus/dave could provide me a patched rc1 exe, i could run it in our
> > semi-productive environment for some tests.
> >
> > - thomas
> >
> >
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
> choose an index scan if your joining column's datatypes do not
> match

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Thomas H. 2006-11-30 14:14:46 Re: fsync and semctl errors with 8.1.5/win32
Previous Message Ilia 2006-11-30 13:33:34 BUG #2795: can't start service postgre