| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Marcin Waldowski <M(dot)Waldowski(at)sulechow(dot)net> |
| Cc: | magnus(at)hagander(dot)net, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #3242: FATAL: could not unlock semaphore: error code 298 |
| Date: | 2007-04-24 06:25:41 |
| Message-ID: | 24451.1177395941@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Marcin Waldowski <M(dot)Waldowski(at)sulechow(dot)net> writes:
> Ok, that's the end of the story :) My workmate has confirmed that during
> night test PostgreSQL worked perfectly :)
That fix was Obviously Necessary even without testing -- you're being
too conservative about not applying it, Magnus.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marcin Waldowski | 2007-04-24 07:10:12 | Re: BUG #3242: FATAL: could not unlock semaphore: error code 298 |
| Previous Message | Marcin Waldowski | 2007-04-24 06:11:36 | Re: BUG #3242: FATAL: could not unlock semaphore: error code 298 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marcin Waldowski | 2007-04-24 07:10:12 | Re: BUG #3242: FATAL: could not unlock semaphore: error code 298 |
| Previous Message | Marcin Waldowski | 2007-04-24 06:11:36 | Re: BUG #3242: FATAL: could not unlock semaphore: error code 298 |