Re: Modest proposal to extend TableAM API for controlling cluster commands - Mailing list pgsql-hackers

From Mark Dilger
Subject Re: Modest proposal to extend TableAM API for controlling cluster commands
Date
Msg-id 1D6CF0FB-D7A8-4524-B09A-46DDCC61EF1A@enterprisedb.com
Whole thread Raw
In response to Re: Modest proposal to extend TableAM API for controlling cluster commands  (Mark Dilger <mark.dilger@enterprisedb.com>)
List pgsql-hackers

> On Jun 15, 2022, at 7:21 PM, Mark Dilger <mark.dilger@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
logicdictates 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
forcustom storage parameters, but Table AMs don't, so getting information to the TAM about how to behave takes more
thana little slight of hand.  Simon's proposal from a while back (don't have the link just now) to allow TAMs to define
customstorage parameters would go some distance here. 

—
Mark Dilger
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company






pgsql-hackers by date:

Previous
From: Mark Dilger
Date:
Subject: Re: Modest proposal to extend TableAM API for controlling cluster commands
Next
From: Andres Freund
Date:
Subject: Re: Modest proposal to extend TableAM API for controlling cluster commands