I've upgraded to 8.2rc1. I still receive fsync errors all the time, but
I haven't had it freeze yet. With 8.1.5 I was able to reproduce the
freeze very quickly, so this is a good sign! Only time will tell if
it's truly resolved - but I'll post updates to this list either way.
I'm still open to
I doubt this is really "a bug." This usually just means that the server
failed to start for some reason (port already in use, bad configuration,
etc.) Any startup problem with the database will result in this
behavior.
However - what might could be addressed is that it is pretty difficult
to deb
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
>
0633937,
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/00010019005E" to
"pg_xlog/000100
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
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
even when no queries are being run (although it might always
start while queries are running)
On Tue, 28 Nov 2006 16:18:56 -0500, "Jeremy Haile" <[EMAIL PROTECTED]>
said:
> OK - after uninstalling the virus scanner (McAfee), I still get the same
> disk access errors.
>
OPENC:\Program
Files\PostgreSQL\8.1\data\base\16404\30267 DELETE PEND Options:
Open Access: 0012019F
This is an incredibly bad problem for me. I'd really appreciate any
help!
Jeremy
On Mon, 27 Nov 2006 12:14:00 -0500, "Jeremy Haile" <[EMAIL PROTECTED]>
said:
>
cs file
"global/pgstat.tmp" to "global/pgstat.stat": No such file or directory
There are no noticeable effects from these errors that I know of. I've
looked at file permissions, etc. and everything seems fine. I've got
FileMon running and don't see anything tha
problems running MySQL/InnoDB on Windows? (since it has
had a native Windows build for much longer)
On Mon, 27 Nov 2006 16:40:57 +, "Dave Page" <[EMAIL PROTECTED]>
said:
> Jeremy Haile wrote:
> > I've gotten pushback from my organization on removing
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?
On Mon, 27 Nov 2006 10:28:23 -0500, "Jeremy Haile" <[EMAIL PROTECTED]>
said:
> Thanks Magnus.
gt; the problem doesn't go away, look for something else installed that
> might be interfernig with the normal operation of your windows install.
>
> //Magnus
>
> > -Original Message-
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED] On Behalf
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
13 matches
Mail list logo
