On Feb 11, 2025 at 07:52 +0800, Sami Imseih , wrote:
>
> IMO, the correct approach is to disallow the STORAGE parameter on
> foreign tables,
> which is what [1] tried to avoid for some reason. However, since this
> behavior has
> existed for over 10 years, I don’t think we should change it.
Hi,
I
> This form sets the storage mode for a column. See the similar form of ALTER
> TABLE for more details.
> Note that the storage mode has no effect unless the table's foreign-data
> wrapper chooses to pay attention to it.
Hi,
It looks like cb1ca4d [1], from nearly 10 years ago, allowed storage
o
Hi,
While developing the CREATE FOREIGN TABLE LIKE functionality in [0], I had to
consider the like_options, such as STORAGE, COMPRESSION, and others.
Although foreign tables do not have actual storage in PostgreSQL, we allow the
STORAGE option as it may be useful for foreign data wrappers (FD
