Re: [HACKERS] GSoC 2017: weekly progress reports (week 6)

Поиск
Список
Период
Сортировка
От Alvaro Herrera
Тема Re: [HACKERS] GSoC 2017: weekly progress reports (week 6)
Дата
Msg-id 20180307173017.6hdvs24wm3ckqnkj@alvherre.pgsql
обсуждение исходный текст
Ответ на Re: [HACKERS] GSoC 2017: weekly progress reports (week 6)  (Shubham Barai <shubhambaraiss@gmail.com>)
Ответы Re: [HACKERS] GSoC 2017: weekly progress reports (week 6)  (Shubham Barai <shubhambaraiss@gmail.com>)
Re: [HACKERS] GSoC 2017: weekly progress reports (week 6)  (Alexander Korotkov <a.korotkov@postgrespro.ru>)
Список pgsql-hackers
I suggest to create a new function GinPredicateLockPage() that checks
whether fast update is enabled for the index.  The current arrangement
looks too repetitive and it seems easy to make a mistake.

Stylistically, please keep #include lines ordered alphabetically, and
cut long lines to below 80 chars.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


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

Предыдущее
От: Alvaro Herrera
Дата:
Сообщение: Re: FOR EACH ROW triggers on partitioned tables
Следующее
От: Andres Freund
Дата:
Сообщение: Re: GSoC 2017: weekly progress reports (week 6)