Re: [PROPOSAL] Use SnapshotAny in get_actual_variable_range

From: Vladimir Borodin <root(at)simply(dot)name>
To: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Cc: Хомик Кирилл <khomikki(at)yandex-team(dot)ru>, Dmitriy Sarafannikov <dsarafannikov(at)yandex(dot)ru>
Subject: Re: [PROPOSAL] Use SnapshotAny in get_actual_variable_range
Date: 2017-05-02 16:37:44
Message-ID: 55E51324-7F80-4282-829D-942431B2C88C@simply.name
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi.

> 25 апр. 2017 г., в 18:13, Dmitriy Sarafannikov <dsarafannikov(at)yandex(dot)ru> написал(а):
>
> I'd like to propose to search min and max value in index with SnapshotAny in get_actual_variable_range function.
> Current implementation scans index with SnapshotDirty which accepts uncommitted rows and rejects dead rows.

The patch is already being discussed here [1].

[1] https://www.postgresql.org/message-id/05C72CF7-B5F6-4DB9-8A09-5AC897653113%40yandex.ru

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2017-05-02 16:45:35 Re: Concurrent ALTER SEQUENCE RESTART Regression
Previous Message David Fetter 2017-05-02 16:34:07 Re: CTE inlining