| From: | Francisco Olarte <folarte(at)peoplecall(dot)com> |
|---|---|
| To: | pawel(dot)samysev(at)gmail(dot)com |
| Cc: | "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #13635: Interlocks at selection with array_agg |
| Date: | 2015-09-24 16:43:16 |
| Message-ID: | CA+bJJbwpBXRsAXUNkONhZQLd2Mk4CR2QVEkYowA7YtQ-zS=BSA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Hi pawel:
On Thu, Sep 24, 2015 at 11:56 AM, <pawel(dot)samysev(at)gmail(dot)com> wrote:
Not seeing the whole query I cannot say too much but:
> WHERE
> p.phone_id BETWEEN :min AND :max
¿ Are you sure you're not getting fencepost overlaps when substituting
:min/:max ? ( between does closed intervals, normally half closed (
phone_id >= min and phone_id<max ) are used for this kinds of queries
( I ask because it seems a query doing b-c could lock out other doing
a-b for a long time ).
Francisco Olarte.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | jeff.janes | 2015-09-24 20:25:45 | BUG #13636: psql numericlocale adds comma where it ought not |
| Previous Message | pawel.samysev | 2015-09-24 09:56:26 | BUG #13635: Interlocks at selection with array_agg |