We've been running in prod without trouble under 'read committed' for
about a week, though not under heavy load -- it's a fairly new site.
I'm not sure how much assurance I can offer at higher load, sorry.
On Fri, Sep 2, 2011 at 11:42 AM, Ian Clelland wrote:
>
>
> On Fri, Sep 2, 2011 at 11:22 AM
On Fri, Sep 2, 2011 at 11:22 AM, Jeremy Dunck wrote:
> On Fri, Sep 2, 2011 at 11:04 AM, Ian Clelland wrote:
> > I'm seeing errors which I believe are due to a race condition in
> > django.db.models.query.get_or_create, on a fairly high traffic site. Our
> > production servers are running Django
On Fri, Sep 2, 2011 at 11:04 AM, Ian Clelland wrote:
> I'm seeing errors which I believe are due to a race condition in
> django.db.models.query.get_or_create, on a fairly high traffic site. Our
> production servers are running Django 1.2.5, but I don't see any changes in
> the code in trunk that
And, of course, immediately after posting this, I find
http://code.djangoproject.com/ticket/13906, which seems to cover much of the
same area.
Ian
On Fri, Sep 2, 2011 at 11:04 AM, Ian Clelland wrote:
> I'm seeing errors which I believe are due to a race condition in
> django.db.models.query.ge
I'm seeing errors which I believe are due to a race condition in
django.db.models.query.get_or_create, on a fairly high traffic site. Our
production servers are running Django 1.2.5, but I don't see any changes in
the code in trunk that would affect this. (I'm totally willing to construct
a test ca
