Re: alter table set TABLE ACCESS METHOD - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: alter table set TABLE ACCESS METHOD
Date
Msg-id YLq7KsEm63eyH0Yl@paquier.xyz
Whole thread Raw
In response to Re: alter table set TABLE ACCESS METHOD  (Jeff Davis <pgsql@j-davis.com>)
Responses Re: alter table set TABLE ACCESS METHOD
List pgsql-hackers
On Fri, Jun 04, 2021 at 11:26:28AM -0700, Jeff Davis wrote:
> Yes. That's a current requirement, and any AM that doesn't do that is
> already broken (e.g. for INSERT INTO ... SELECT).

Makes sense.  I was just looking at the patch, and this was the only
part of it that made my spidey sense react.

One thing I am wondering is if we should have a dummy_table_am in
src/test/modules/ to be able to stress more this feature.  That does
not seem like a hard requirement, but relying only on heap limits a
bit the coverage of this feature even if one changes
default_table_access_method.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: logical decoding bug: segfault in ReorderBufferToastReplace()
Next
From: Michael Paquier
Date:
Subject: installcheck failure in indirect_toast with default_toast_compression = lz4