So what's holding the file open now? It's evidently not the bgwriter.
one of the unnamed postgresql.exe processes from the connection pool:
postgres: db_outnow outnow 127.0.0.1(3384) idle
Hm. I would imagine that as soon as this process does something,
the messages stop? (It should close i
... in addition to the above messages, the log is now also
flooded by:
2006-12-05 04:16:29 [5196] LOG: could not rename temporary statistics
file
"global/pgstat.tmp" to "global/pgstat.stat": A blocking operation was
interrupted by a call to WSACancelBlockingCall.
Hm ... there simply isn't a
"Thomas H." <[EMAIL PROTECTED]> writes:
> ... in addition to the above messages, the log is now also
> flooded by:
> 2006-12-05 04:16:29 [5196] LOG: could not rename temporary statistics file
> "global/pgstat.tmp" to "global/pgstat.stat": A blocking operation was
> interrupted by a call to WSA
"Thomas H." <[EMAIL PROTECTED]> writes:
>> So what's holding the file open now? It's evidently not the bgwriter.
> one of the unnamed postgresql.exe processes from the connection pool:
> postgres: db_outnow outnow 127.0.0.1(3384) idle
Hm. I would imagine that as soon as this process does someth
2006-12-05 03:47:12 [736] LOG: could not fsync segment 0 of relation
1663/16692/2361629: Permission denied
2006-12-05 03:47:12 [736] ERROR: storage sync failed on magnetic disk:
Permission denied
2006-12-05 03:47:13 [736] ERROR: could not open relation
1663/16692/2361629: Permission denied
20
in 8.2.0 the error messages changed a bit:
2006-12-05 03:47:12 [736] LOG: could not fsync segment 0 of relation
1663/16692/2361629: Permission denied
2006-12-05 03:47:12 [736] ERROR: storage sync failed on magnetic disk:
Permission denied
2006-12-05 03:47:13 [736] ERROR: could not open relat
"Thomas H." <[EMAIL PROTECTED]> writes:
> in 8.2.0 the error messages changed a bit:
> 2006-12-05 03:47:12 [736] LOG: could not fsync segment 0 of relation
> 1663/16692/2361629: Permission denied
> 2006-12-05 03:47:12 [736] ERROR: storage sync failed on magnetic disk:
> Permission denied
> 200
Here's a few seconds of the log output (this has been going on for 10
mins as of this e-mail being sent):
2006-11-28 16:16:10 LOG: could not fsync segment 0 of relation
1663/16404/30267: Permission denied
2006-11-28 16:16:10 ERROR: storage sync failed on magnetic disk:
Permission denied
Here'
OTECTED]
> Sent: Thursday, November 30, 2006 10:04 AM
> To: Bradley Russell
> Cc: pgsql-bugs@postgresql.org
> Subject: Re: [BUGS] fsync and semctl errors with 8.1.5/win32
>
>
> > We were also running it on Windows Server 2003. We ended up rolling
> > back service pa
.
-Original Message-
From: Thomas H. [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 30, 2006 10:04 AM
To: Bradley Russell
Cc: pgsql-bugs@postgresql.org
Subject: Re: [BUGS] fsync and semctl errors with 8.1.5/win32
> We were also running it on Windows Server 2003. We ended up roll
-bugs@postgresql.org
Subject: Re: [BUGS] fsync and semctl errors with 8.1.5/win32
> Did you run into problems where transactions would hang? If so, did
> those disappear in 8.2?
well, i wasn't really able to exactly determine under what conditions
that
xlog bug appeared in our cas
We were also running it on Windows Server 2003. We ended up rolling
back service pack 1 and it seems to have taken care of the hanging
transactions and we haven't seen a semctl error in awhile.
interesting. we're using sp1 & pgsql since day 1 and the problem only
started when testing 8.2b1. bu
Did you run into problems where transactions would hang? If so, did
those disappear in 8.2?
well, i wasn't really able to exactly determine under what conditions that
xlog bug appeared in our case. tho it always was when lots of data is
imported at once within one transaction. under normal lo
Really? That's great news. Maybe I should start testing with 8.2
today.
Did you run into problems where transactions would hang? If so, did
those disappear in 8.2?
On Thu, 30 Nov 2006 15:14:46 +0100, "Thomas H." <[EMAIL PROTECTED]> said:
> > 2006-11-29 23:57:52 LOG: could not rename file
>
2006-11-29 23:57:52 LOG: could not rename file
"pg_xlog/00010019005E" to
"pg_xlog/00010019007F", continuing to try
i had this one as well. good news is: this bug is fixed in 8.2
- thomas
---(end of broadcast)---
TIP 5: d
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 unt
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." <[EMAIL PROTECTED]> said:
> > Perhaps this should be #ifdef WIN32, although there's probably no harm
> > in doi
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
Yes - processmon always shows the files being locked by postgres.exe
processes. My database is being used as a data warehouse, so about all
I am doing is bulk insert/updates. I have a job that runs every 5
minutes and loads data into the database.
I typically load between 10,000 and 100,000 r
"Jeremy Haile" <[EMAIL PROTECTED]> writes:
> Here's a few seconds of the log output (this has been going on for 10
> mins as of this e-mail being sent):
> 2006-11-28 16:16:10 LOG: could not fsync segment 0 of relation
> 1663/16404/30267: Permission denied
> 2006-11-28 16:16:10 ERROR: storage sync
I forgot to mention - this problem is occurring on multiple Windows
machines. One of them is running Windows XP Professional. The other is
running Windows Server 2003. I have disabled indexing, virus scanning,
and all non-essential services on both of them. The problem continues
to show up eve
I forgot to mention - this problem is occurring on multiple Windows
machines. One of them is running Windows XP Professional. The other is
running Windows Server 2003. I have disabled indexing, virus scanning,
and all non-essential services on both of them. The problem continues
to show up even
OK - after uninstalling the virus scanner (McAfee), I still get the same
disk access errors.
Here's a few seconds of the log output (this has been going on for 10
mins as of this e-mail being sent):
2006-11-28 16:16:10 LOG: could not fsync segment 0 of relation
1663/16404/30267: Permission denied
Thanks for the feedback. If you don't mind, what version of PostgreSQL
are you running?
I'm trying to bring PostgreSQL into this company - they are primarily a
Windows/SQL Server shop (although Java software development) I've
already gotten comments similar to "Why don't you just switch to SQL
S
Jeremy Haile wrote:
I've gotten pushback from my organization on removing antivirus from the
servers completely. Are there any antiviruses that are known to be
compatible with PostgreSQL/win32?
All my boxes (2 build farm members, 1 production server, and the laptop
on which the official rel
ginal Message-
> > > From: [EMAIL PROTECTED]
> > > [mailto:[EMAIL PROTECTED] On Behalf Of Jeremy Haile
> > > Sent: den 27 november 2006 15:21
> > > To: pgsql-bugs@postgresql.org
> > > Subject: [BUGS] fsync and semctl errors with 8.1.5/win32
> >
Of Jeremy Haile
> > Sent: den 27 november 2006 15:21
> > To: pgsql-bugs@postgresql.org
> > Subject: [BUGS] fsync and semctl errors with 8.1.5/win32
> >
> > I've been attempting to run PostgreSQL 8.1.5/win32 on a
> > production deployment, but have st
> To: pgsql-bugs@postgresql.org
> Subject: [BUGS] fsync and semctl errors with 8.1.5/win32
>
> I've been attempting to run PostgreSQL 8.1.5/win32 on a
> production deployment, but have started having many problems.
> McAfee Antivirus is installed and running, although
I've been attempting to run PostgreSQL 8.1.5/win32 on a production
deployment, but have started having many problems. McAfee Antivirus is
installed and running, although I've excluded the entire drive where
PostgreSQL is installed and where the data is installed.
I've received several errors in t
29 matches
Mail list logo
