Re: [PATCHES] [BUGS] [Win32] Problem with rename()
On 16.06.2006 at 23:21:21, in message [EMAIL PROTECTED], Bruce Momjian pgman@candle.pha.pa.us wrote: Yea. Where you using WAL archiving? We will have a fix in 8.1.5 to prevent multiple archivers from starting. Perhaps that was a cause. Not at the time, no. The rename in question was just a regular WAL segment rename. Yes, I just reread that thread. I also am confused where to go from here. Yeah, it's unfortunate that our best theory (a _commit on a deleted file) just didn't seem to be supported by the evidence. Although the servers which see a heavy SELECT load are now Linux, we still have a couple of Windows servers receiving the normal replication traffic. We still get regular fsync errors after the scheduled CLUSTERs so if you do find a fix (or come up with a new theory), there's a test bed there (at least for now). Were you the only one use Win32 in heavy usage? You were on Win2003. Were there some bugs in the OS that got fixed later. ... Yep. What has me baffled is why no one else is seeing the problem. We had a rash of reports, and now all is quiet. We might be somewhat more susceptible than most too. Due to the way our middle tier parcels out queries, some connections might sit idle for a long time. Per Tom's explanation in the original thread, this is an important factor. Ultimately if a concurrent rename isn't possible in Windows (and that looks likely), it's going to be a problem as things stand now. Pete ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [PATCHES] [BUGS] [Win32] Problem with rename()
Really? If there was a patch, I missed it. My recollection is that there was general agreement about this particular problem (see, for example, http://archives.postgresql.org/pgsql-bugs/2006-04/msg00189.php ), but things kind of trailed off after that without a resolution. As far as the complete list of Win32 problems which affected us: - The stats collector crashing should indeed be fixed in 8.1.4 - Missing stats caused by Windows PID recycling is fixed in 8.2 - Various semaphore problems are probably all fixed with the new Win32 semaphore implementation in 8.2 - The stuck log rename problem mentioned above is still an issue - The permission denied on fsync (or something like that) problem is still an issue. Unfortunately, IIRC, we could never really nail down the underlying problem. None of these problems affect us any more: the production servers now run Linux. Great to have options! (and we were moving that direction anyway) Pete Bruce Momjian pgman@candle.pha.pa.us 16.06.2006 22:05 I am assuming this problem and the other rash of Win32 problems reported in March are now all fixed in 8.1.4. If not, please let me know. ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [PATCHES] [BUGS] [Win32] Problem with rename()
Peter Brant wrote: Really? If there was a patch, I missed it. My recollection is that there was general agreement about this particular problem (see, for example, http://archives.postgresql.org/pgsql-bugs/2006-04/msg00189.php ), but things kind of trailed off after that without a resolution. Yea. Where you using WAL archiving? We will have a fix in 8.1.5 to prevent multiple archivers from starting. Perhaps that was a cause. As far as the complete list of Win32 problems which affected us: - The stats collector crashing should indeed be fixed in 8.1.4 - Missing stats caused by Windows PID recycling is fixed in 8.2 - Various semaphore problems are probably all fixed with the new Win32 semaphore implementation in 8.2 - The stuck log rename problem mentioned above is still an issue Yep. What has me baffled is why no one else is seeing the problem. We had a rash of reports, and now all is quiet. - The permission denied on fsync (or something like that) problem is still an issue. Unfortunately, IIRC, we could never really nail down the underlying problem. Yes, I just reread that thread. I also am confused where to go from here. None of these problems affect us any more: the production servers now run Linux. Great to have options! (and we were moving that direction anyway) Were you the only one use Win32 in heavy usage? You were on Win2003. Were there some bugs in the OS that got fixed later. Yea, stumped. Guess we will have to wait for more reports. I don't even see how to document this as a TODO. -- Bruce Momjian http://candle.pha.pa.us EnterpriseDBhttp://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---(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
