From: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
---|---|
To: | MauMau <maumau307(at)gmail(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-13 07:47:29 |
Message-ID: | 543B8391.6060909@vmware.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 10/10/2014 05:08 PM, MauMau wrote:
> From: "Craig Ringer" <craig(at)2ndquadrant(dot)com>
>> It sounds like they've produced a test case, so they should be able to
>> with a bit of luck.
>>
>> Or even better, send you the test case.
>
> I asked the user about this. It sounds like the relevant test case consists
> of many scripts. He explained to me that the simplified test steps are:
>
> 1. initdb
> 2. pg_ctl start
> 3. Create 16 tables. Each of those tables consist of around 10 columns.
> 4. Insert 1000 rows into each of those 16 tables.
> 5. Launch 16 psql sessions concurrently. Each session updates all 1000 rows
> of one table, e.g., session 1 updates table 1, session 2 updates table 2,
> and so on.
> 6. Repeat step 5 50 times.
>
> This sounds a bit complicated, but I understood that the core part is 16
> concurrent updates, which should lead to contention on xlog insert slots
> and/or spinlocks.
I was able to reproduce this. I reduced wal_buffers to 64kB, and
NUM_XLOGINSERT_LOCKS to 4 to increase the probability of the deadlock,
and ran a test case as above on my laptop for several hours, and it
finally hung. Will investigate...
- Heikki
From | Date | Subject | |
---|---|---|---|
Next Message | Sawada Masahiko | 2014-10-13 08:39:45 | Re: Proposal : REINDEX SCHEMA |
Previous Message | Albe Laurenz | 2014-10-13 07:36:19 | Re: WIP: multivariate statistics / proof of concept |