| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Shubham Barai <shubhambaraiss(at)gmail(dot)com> |
| Cc: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Andrew Borodin <amborodin86(at)gmail(dot)com>, Kevin Grittner <kgrittn(at)gmail(dot)com> |
| Subject: | Re: [HACKERS] GSoC 2017: weekly progress reports (week 6) |
| Date: | 2018-03-07 17:30:17 |
| Message-ID: | 20180307173017.6hdvs24wm3ckqnkj@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-www |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2018-03-07 17:34:44 | Re: GSoC 2017: weekly progress reports (week 6) |
| Previous Message | Alvaro Herrera | 2018-03-07 17:17:53 | Re: FOR EACH ROW triggers on partitioned tables |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2018-03-07 17:34:44 | Re: GSoC 2017: weekly progress reports (week 6) |
| Previous Message | Alvaro Herrera | 2018-03-07 14:58:51 | Re: GSoC 2017: weekly progress reports (week 6) |