> On Jun 15, 2022, at 7:21 PM, Mark Dilger <mark.dil...@enterprisedb.com> wrote:
>
>> If a user does that for a table that doesn't support clustering, well, I
>> don't
>> see what's gained by not erroring out.
>
> Perhaps they want to give the TAM information about which index to use for
> sorting, on those occasions when the TAM's logic dictates that sorting is
> appropriate, but not in response to a cluster command.
I should admit that this is a bit hack-ish, but TAM authors haven't been left a
lot of options here. Index AMs allow for custom storage parameters, but Table
AMs don't, so getting information to the TAM about how to behave takes more
than a little slight of hand. Simon's proposal from a while back (don't have
the link just now) to allow TAMs to define custom storage parameters would go
some distance here.
—
Mark Dilger
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
