| From: | Andy Fan <zhihui(dot)fan1213(at)gmail(dot)com> |
|---|---|
| To: | Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com> |
| Cc: | David Rowley <dgrowleyml(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, rushabh(dot)lathia(at)gmail(dot)com, Ashutosh Bapat <ashutosh(dot)bapat(at)2ndquadrant(dot)com> |
| Subject: | Re: [PATCH] Keeps tracking the uniqueness with UniqueKey |
| Date: | 2020-05-14 02:46:27 |
| Message-ID: | CAKU4AWpjj1-fJzJPN6DgmmBOkRrChsb8hYR4gHi1CaVwsu+M8Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, May 13, 2020 at 11:48 PM Andy Fan <zhihui(dot)fan1213(at)gmail(dot)com> wrote:
>
>> My impression about the one row stuff, is that there is too much
>> special casing around it. We should somehow structure the UniqueKey
>> data so that one row unique keys come naturally rather than special
>> cased. E.g every column in such a case is unique in the result so
>> create as many UniqueKeys are the number of columns
>
>
> This is the beginning state of the UniqueKey, later David suggested
> this as an optimization[1], I buy-in the idea and later I found it mean
> more than the original one [2], so I think onerow is needed actually.
>
>
I just found I forget the links yesterday. Here is it.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-05-14 02:52:29 | Re: Another modest proposal for docs formatting: catalog descriptions |
| Previous Message | Kyotaro Horiguchi | 2020-05-14 02:43:19 | Re: tablespace_map code cleanup |