Re: Per-table storage parameters for TableAM/IndexAM extensions
От | Simon Riggs |
---|---|
Тема | Re: Per-table storage parameters for TableAM/IndexAM extensions |
Дата | |
Msg-id | CANbhV-FdqrOT4tOp7q=qqCno5SY7+aLWK-v-zpfzdCw43sN4wA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Per-table storage parameters for TableAM/IndexAM extensions (Sadhuprasad Patro <b.sadhu@gmail.com>) |
Ответы |
Re: Per-table storage parameters for TableAM/IndexAM extensions
|
Список | pgsql-hackers |
On Thu, 17 Feb 2022 at 17:55, Sadhuprasad Patro <b.sadhu@gmail.com> wrote: > > > On Sat, Feb 12, 2022 at 2:35 AM Robert Haas <robertmhaas@gmail.com> wrote: > >> > >> > >> Imagine that I am using the "foo" tableam with "compression=lots" and > >> I want to switch to the "bar" AM which does not support that option. > >> If I remove the "compression=lots" option using a separate command, > >> the "foo" table AM may rewrite my whole table and decompress > >> everything. Then when I convert to the "bar" AM it's going to have to > >> be rewritten again. That's painful. I clearly need some way to switch > >> AMs without having to rewrite the table twice. > > > Agreed. Better to avoid multiple rewrites here. Thank you for figuring out this. > > > > You'd need to be able to do multiple things with one command e.g. > > > ALTER TABLE mytab SET ACCESS METHOD baz RESET compression, SET > > preferred_fruit = 'banana'; > > +1 > Silently dropping some options is not right and it may confuse users > too. So I would like to go > for the command you have suggested, where the user should be able to > SET & RESET multiple > options in a single command for an object. I prefer ADD/DROP to SET/RESET. The latter doesn't convey the meaning accurately to me. -- Simon Riggs http://www.EnterpriseDB.com/
В списке pgsql-hackers по дате отправления: