| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Junwang Zhao <zhjwpku(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, nik(at)postgres(dot)ai, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #18244: Corruption in indexes involving whole-row expressions |
| Date: | 2023-12-14 08:44:33 |
| Message-ID: | c56c11e52620ea3a51f13aa482ac2376a3c552e8.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Thu, 2023-12-14 at 16:27 +0800, Junwang Zhao wrote:
> + While you can use composite types in column definitions, there is usually no
> + benefit in doing so.
>
> Is this true? If yes, we'd better update this to
> https://wiki.postgresql.org/wiki/Don%27t_Do_This.
I cannot think of a use case for composite type columns that wouldn't be
better served by directly declaring the columns of the composite key
in the table definition. And it makes accessing the values more complicated.
So yes, I'd be on board with a "don't do this" entry.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Richard Guo | 2023-12-14 10:34:44 | Re: BUG #18247: Integer overflow leads to negative width |
| Previous Message | Junwang Zhao | 2023-12-14 08:27:31 | Re: BUG #18244: Corruption in indexes involving whole-row expressions |