Re: Global snapshots

Поиск
Список
Период
Сортировка
От Dmitry Dolgov
Тема Re: Global snapshots
Дата
Msg-id CA+q6zcWk-JP+ZEmqPe5Uaaqg39a8w8VueBFw+5z+Jq_iWV5TYA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Global snapshots  (Arseny Sher <a.sher@postgrespro.ru>)
Ответы Re: Global snapshots  (Stas Kelvich <s.kelvich@postgrespro.ru>)
Список pgsql-hackers
> On Wed, Jul 25, 2018 at 1:35 PM Arseny Sher <a.sher@postgrespro.ru> wrote:
>
> Hello,
>
> I have looked through the patches and found them pretty accurate. I'd
> fixed a lot of small issues here and there; updated patchset is
> attached.

Hi,

Thank you for working on this patch. Unfortunately, the patch has some
conflicts, could you please rebase it? Also I wonder if you or Stas can shed
some light about this:

> On Wed, May 16, 2018 at 2:02 PM Stas Kelvich <s.kelvich@postgrespro.ru> wrote:
> > On 15 May 2018, at 15:53, Robert Haas <robertmhaas@gmail.com> wrote:
> >
> > I guess it seems to me that you
> > have some further research to do along the lines you've described:
> >
> > 1. Can we hold back xmin only when necessary and to the extent
> > necessary instead of all the time?
> > 2. Can we use something like an STO analog, maybe as an optional
> > feature, rather than actually holding back xmin?
>
> Yes, to both questions. I'll implement that and share results.

Is there any resulting patch where the ideas how to implement this are outlined?


В списке pgsql-hackers по дате отправления:

Предыдущее
От: "Bossart, Nathan"
Дата:
Сообщение: Re: Use durable_unlink for .ready and .done files for WAL segmentremoval
Следующее
От: Dmitry Dolgov
Дата:
Сообщение: Re: [PATCH] kNN for btree