| From: | "Bradley Russell" <bradley(dot)russell(at)npcinternational(dot)com> |
|---|---|
| To: | "'Thomas H(dot)'" <me(at)alternize(dot)com> |
| Cc: | <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: fsync and semctl errors with 8.1.5/win32 |
| Date: | 2006-11-30 16:15:50 |
| Message-ID: | 008e01c7149a$cd2ff5e0$4a0a10ac@npci.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
In our case the hanging transactions was killing our in house merge
process that merges the data from our stores to the warehouse.
When we rolled back sp1 no hanging transactions. When we applied sp1
the hanging started again. We took sp1 off and on a couple times and it
happened every time.
-----Original Message-----
From: Thomas H. [mailto:me(at)alternize(dot)com]
Sent: Thursday, November 30, 2006 10:04 AM
To: Bradley Russell
Cc: pgsql-bugs(at)postgresql(dot)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 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. but on the other hand, it might be that a
hotfix
is the cause for this error, as i haven't seen it before aug/sept 06. i
sure
would have noticed...
- thomas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeremy Haile | 2006-11-30 17:11:34 | Re: BUG #2795: can't start service postgre |
| Previous Message | Thomas H. | 2006-11-30 16:03:48 | Re: fsync and semctl errors with 8.1.5/win32 |