Re: Error position support for ComputeIndexAttrs

2025-12-16 Thread Amul Sul
limit, CREATE INDEX can be as complicated as PARTITION BY expression, and > given > that ComputeIndexAttrs already contains 14 calls to ereport(ERROR, ...). > Adding error position support for ComputeIndexAttrs seems to make sense. > > To achieve this, ComputeIndexAttrs must receive

Error position support for ComputeIndexAttrs

2025-12-15 Thread jian he
ComputeIndexAttrs already contains 14 calls to ereport(ERROR, ...). Adding error position support for ComputeIndexAttrs seems to make sense. To achieve this, ComputeIndexAttrs must receive a ParseState. Since ComputeIndexAttrs is nested under DefineIndex , DefineIndex must also have a ParseState. v1