| From: | Shubham Barai <shubhambaraiss(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(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-08 12:40:09 |
| Message-ID: | CALxAEPt1SSMx-dBTrU=G9CDTHJoCH_V+O4tdDFvs1Jv6JXtyYQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-www |
On 07-Mar-2018 11:00 PM, "Alvaro Herrera" <alvherre(at)2ndquadrant(dot)com> wrote:
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.
Okay, I will update the patch.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavan Deolasee | 2018-03-08 12:54:25 | Re: [HACKERS] MERGE SQL Statement for PG11 |
| Previous Message | amul sul | 2018-03-08 12:08:24 | Re: [HACKERS] Restrict concurrent update/delete with UPDATE of partition key |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2018-03-09 21:52:26 | Re: planning for perf farm app |
| Previous Message | Andres Freund | 2018-03-07 17:34:44 | Re: GSoC 2017: weekly progress reports (week 6) |