Re: can we add SKIP LOCKED to UPDATE?

From: Craig Ringer <craig(at)2ndquadrant(dot)com>
To: Torsten Zühlsdorff <mailinglists(at)toco-domains(dot)de>
Cc: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 德哥 <digoal(at)126(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: can we add SKIP LOCKED to UPDATE?
Date: 2015-11-11 13:07:46
Message-ID: CAMsr+YG5xfi6h-P6HRMw1+bMO0_eXAbaJGmAKf4ze-cOHwzpEg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 11 November 2015 at 16:02, Torsten Zühlsdorff <
mailinglists(at)toco-domains(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2015-11-11 13:53:58 Re: proposal: numeric scale functions
Previous Message Ildus Kurbangaliev 2015-11-11 11:50:59 Re: [PATCH] Refactoring of LWLock tranches