| From: | Anastasia Lubennikova <a(dot)lubennikova(at)postgrespro(dot)ru> |
|---|---|
| To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Cc: | Justin Pryzby <justin(at)telsasoft(dot)com> |
| Subject: | Re: bitmaps and correlation |
| Date: | 2020-11-06 13:51:26 |
| Message-ID: | 160467068611.7362.8226463259534237605.pgcf@coridan.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Status update for a commitfest entry
According to cfbot, the patch fails to apply. Could you please send a rebased version?
I wonder why this patch hangs so long without a review. Maybe it will help to move discussion forward, if you provide more examples of queries that can benefit from this imporovement?
The first patch is simply a refactoring and don't see any possible objections against it.
The second patch also looks fine to me. The logic is understandable and the code is neat.
It wouldn't hurt to add a comment for this computation, though.
+ pages_fetched = pages_fetchedMAX + indexCorrelation*indexCorrelation*(pages_fetchedMIN - pages_fetchedMAX);
The new status of this patch is: Waiting on Author
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andy Fan | 2020-11-06 14:20:16 | Re: Advance xmin aggressively on Read Commit isolation level |
| Previous Message | Michael Paquier | 2020-11-06 13:27:12 | Re: Move OpenSSL random under USE_OPENSSL_RANDOM |