From: | Steve Lau <stevelauc(at)outlook(dot)com> |
---|---|
To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "david(dot)g(dot)johnston(at)gmail(dot)com" <david(dot)g(dot)johnston(at)gmail(dot)com>, "pgsql-docs(at)postgresql(dot)org" <pgsql-docs(at)postgresql(dot)org> |
Subject: | Re: Index of expression over table row or column |
Date: | 2024-10-16 06:14:25 |
Message-ID: | 3D517897-C6B8-4BAC-A3ED-100B17D6577E@outlook.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
Hi
> On Oct 16, 2024, at 12:17 PM, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> wrote:
>
> And what would you say about this (silly) example:
>
> CREATE TABLE x (a integer, b integer);
> CREATE INDEX ON x(hash_record(x));
When I talk about an expression over something, I mainly think about it at the AST level, I guess the AST of expression “hash_record(x)” will be something like (I tried to parse this statement and print the AST using pg_query.rs, but looks like this library does not have an AST type defined, sorry if my guess is too incorrect):
FunctionCall {
name: “hash_record",
arguments: [
Table {
name: "x"
}
]
}
So it is not table columns or rows IMHO.
Regards, Steve.
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2024-10-16 07:07:13 | Re: Limitation relates to memory allocation |
Previous Message | Laurenz Albe | 2024-10-16 04:17:01 | Re: Index of expression over table row or column |