| From: | Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Shubham Barai <shubhambaraiss(at)gmail(dot)com>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, 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-11 20:54:31 |
| Message-ID: | CAPpHfdu6BPbhJSBAJ_5HLvA1S1Dp2+M4sgRYgqOodv7_RE0NaA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-www |
On Wed, Mar 7, 2018 at 8:30 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.
>
BTW, should we also skip CheckForSerializableConflictIn() when
fast update is enabled? AFAICS, now it doesn't cause any errors or
false positives, but makes useless load. Is it correct?
------
Alexander Korotkov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2018-03-11 22:39:10 | Re: [bug fix] pg_rewind creates corrupt WAL files, and the standby cannot catch up the primary |
| Previous Message | Andres Freund | 2018-03-11 20:51:40 | Re: Using JIT for VACUUM, COPY, ANALYZE |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-03-11 21:15:42 | Re: Bogus reports from coverage.postgresql.org |
| Previous Message | Magnus Hagander | 2018-03-11 20:32:56 | Re: Bogus reports from coverage.postgresql.org |