Re: [HACKERS] Patch: Write Amplification Reduction Method (WARM)

Поиск
Список
Период
Сортировка
От Pavan Deolasee
Тема Re: [HACKERS] Patch: Write Amplification Reduction Method (WARM)
Дата
Msg-id CABOikdMPV=Bo814Kywm4Z9_JmvMCopKDAb0vDrsDmyqZzwvmnw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [HACKERS] Patch: Write Amplification Reduction Method (WARM)  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Ответы Re: [HACKERS] Patch: Write Amplification Reduction Method (WARM)  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Re: [HACKERS] Patch: Write Amplification Reduction Method (WARM)  (Pavan Deolasee <pavan.deolasee@gmail.com>)
Список pgsql-hackers


On Wed, Feb 1, 2017 at 3:21 AM, Alvaro Herrera <alvherre@2ndquadrant.com> wrote:
Alvaro Herrera wrote:

> Unless there are objections I will push this later this afternoon.

Done.  Let's get on with the show -- please post a rebased WARM.


Please see rebased patches attached. There is not much change other than the fact the patch now uses new catalog maintenance API. 

Do you think we should apply the patch to remove ItemPointerCopy()? I will rework the HeapTupleHeaderGetNextTid() after that. Not that it depends on removing ItemPointerCopy(), but decided to postpone it until we make a call on that patch.

BTW I've run now long stress tests with the patch applied and see no new issues, even when indexes are dropped and recreated concurrently (includes my patch to fix CIC bug in the master though). In another 24 hour test, WARM could do 274M transactions where as master did 164M transactions. I did not drop and recreate indexes during this run. 

Thanks,
Pavan

--
 Pavan Deolasee                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services
Вложения

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

Предыдущее
От: Amit Kapila
Дата:
Сообщение: Re: [HACKERS] Index corruption with CREATE INDEX CONCURRENTLY
Следующее
От: Magnus Hagander
Дата:
Сообщение: Re: [HACKERS] Enabling replication connections by default in pg_hba.conf