Re: can we add SKIP LOCKED to UPDATE? - Mailing list pgsql-hackers

From Craig Ringer
Subject Re: can we add SKIP LOCKED to UPDATE?
Date
Msg-id CAMsr+YG5xfi6h-P6HRMw1+bMO0_eXAbaJGmAKf4ze-cOHwzpEg@mail.gmail.com
Whole thread Raw
In response to Re: can we add SKIP LOCKED to UPDATE?  (Torsten Zühlsdorff <mailinglists@toco-domains.de>)
Responses Re: can we add SKIP LOCKED to UPDATE?  (Gavin Flower <GavinFlower@archidevsys.co.nz>)
List pgsql-hackers


On 11 November 2015 at 16:02, Torsten Zühlsdorff <mailinglists@toco-domains.de> wrote:
 
>From my experience most databases are just tpo small. Their operations finish before there can be a deadlock. Same for race conditions - most developer don't know about them, because they never stumbled upon them. I am matching regularly discussions if a database is already to big when holding 10.000 records in the whole cluster...

Ha. Yes. So true.

I see Stack Overflow posts where somebody explains that their query takes ages on their Huge!!1! database. Then it turns out the query takes 0.2 seconds on a 400MB table.

Huge. Right.

--
 Craig Ringer                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

pgsql-hackers by date:

Previous
From: Ildus Kurbangaliev
Date:
Subject: Re: [PATCH] Refactoring of LWLock tranches
Next
From: Peter Eisentraut
Date:
Subject: Re: proposal: numeric scale functions