| From: | zhihuifan1213(at)163(dot)com |
|---|---|
| To: | zhihuifan1213(at)163(dot)com |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, David Rowley <dgrowleyml(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>, jian he <jian(dot)universality(at)gmail(dot)com> |
| Subject: | Re: UniqueKey v2 |
| Date: | 2023-11-09 11:33:34 |
| Message-ID: | 871qczm9oc.fsf@163.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
zhihuifan1213(at)163(dot)com writes:
Hi,
Here is the v3, the mainly changes is it maintains the UniqueKey on
joinrel level, which probabaly is the most important part of this
feature. It shows how the UnqiueKey on joinrel is generated and how it
is discarded due to non-interesting-uniquekey and also show much details
about the single-row case.
I will always maintain README.uniquekey under src/backend/optimizer/path/
to include the latest state of this feature to save the time for
reviewer from going through from the begining. I also use the word "BAD
CASE" in uniquekey.sql to demo which sistuation is not handled well so
far, that probably needs more attention at the first review.
| Attachment | Content-Type | Size |
|---|---|---|
| v3-0001-maintain-uniquekey-on-baserel-joinrel-level-and-u.patch | text/x-diff | 50.2 KB |
| unknown_filename | text/plain | 28 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nazir Bilal Yavuz | 2023-11-09 11:39:26 | Re: Show WAL write and fsync stats in pg_stat_io |
| Previous Message | torikoshia | 2023-11-09 11:26:27 | Re: RFC: Logging plan of the running query |