| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | Rafia Sabih <rafia(dot)sabih(at)enterprisedb(dot)com>, Rahila Syed <rahilasyed90(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Parallel Index-only scan |
| Date: | 2017-02-19 10:32:44 |
| Message-ID: | CA+TgmoZ-xEPW2MzXimZFM=t95Vr6pppzEWQpia75YkNMuuJ+ng@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Feb 18, 2017 at 12:02 PM, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
> + /*
> + * If we are here to just update the scan keys, then don't
> reset parallel
> + * scan. For detailed reason behind this look in the comments for
> + * ExecReScanIndexScan.
> + */
>
> You can phrase the second line as "See ExecReScanIndexScan for
> details.". Apart from that this patch looks good to me. I have
> marked this patch as "Ready For Committer".
Committed, although I neglected to incorporate this change. Not sure
if I should go back and do that; it doesn't read too badly as-is.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2017-02-19 11:03:36 | Re: Provide list of subscriptions and publications in psql's completion |
| Previous Message | Pavan Deolasee | 2017-02-19 10:22:54 | Re: Index corruption with CREATE INDEX CONCURRENTLY |