From: | "MauMau" <maumau307(at)gmail(dot)com> |
---|---|
To: | "Heikki Linnakangas" <hlinnakangas(at)vmware(dot)com> |
Cc: | "Andres Freund" <andres(at)2ndquadrant(dot)com>, "Craig Ringer" <craig(at)2ndquadrant(dot)com>, <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [9.4 bug] The database server hangs with write-heavy workload on Windows |
Date: | 2014-10-15 12:03:42 |
Message-ID: | C14E24B014CB434EA821DE702EEC3253@maumau |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
From: "MauMau" <maumau307(at)gmail(dot)com>
> Thank you very much. I didn't anticipate such a difficult complicated
> cause. The user agreed to try the patch tonight. I'll report back the
> result as soon as I got it from him.
The test ran successfully without hang for 24 hours. It was run with your
patch + the following:
> BTW, in LWLockWaitForVar(), the first line of the following code fragment
> is not necessary, because lwWaitLink is set to head immediately. I think
> it would be good to eliminate as much unnecessary code as possible from
> the spinlock section.
>
> proc->lwWaitLink = NULL;
>
> /* waiters are added to the front of the queue */
> proc->lwWaitLink = lock->head;
>
Regards
MauMau
From | Date | Subject | |
---|---|---|---|
Next Message | Alexander Korotkov | 2014-10-15 12:08:38 | WIP: Access method extendability |
Previous Message | Lucas Lersch | 2014-10-15 11:49:21 | Re: Buffer Requests Trace |