Re: Scaling up deferred unique checks and the after trigger queue

From: Dean Rasheed <dean(dot)a(dot)rasheed(at)googlemail(dot)com>
To: Jeff Davis <pgsql(at)j-davis(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Scaling up deferred unique checks and the after trigger queue
Date: 2009-10-26 17:23:25
Message-ID: 8e2dbb700910261023j5c4e9ae4j7efa3e10ba02c39f@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2009/10/26 Jeff Davis <pgsql(at)j-davis(dot)com>:
> On Mon, 2009-10-26 at 13:41 +0000, Dean Rasheed wrote:
>> I did a quick bit of testing, and I think that there is a
>> locking/concurrency problem :-(
>
> Unfortunately I can't reproduce the problem on my machine; it always
> passes.
>

That's odd. It happens every time on my machine (10 threads, 1000 loops).

> If you have a minute, can you try to determine if the problem can happen
> with a non-deferrable constraint?
>

If anything, that seems to make it fail more quickly.

If it's of any relevance, I'm currently using an optimised build, with
assert checking off.
[Linux x86_64, 2 core Intel Core2]

- Dean

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2009-10-26 17:24:07 Re: Parsing config files in a directory
Previous Message Greg Stark 2009-10-26 17:22:28 Re: a question about relkind of RelationData handed over to heap_update function