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

From Jeff Davis
Subject Re: alter table set TABLE ACCESS METHOD
Date
Msg-id e19c27eeac61434ac3df3f1c3109217a4f14808c.camel@j-davis.com
Whole thread Raw
In response to Re: alter table set TABLE ACCESS METHOD  (Michael Paquier <michael@paquier.xyz>)
Responses Re: alter table set TABLE ACCESS METHOD  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
On Fri, 2021-06-04 at 14:58 +0900, Michael Paquier wrote:
> In short, a table AMs would receive on a rewrite with ALTER TABLE
> tuples which may be toasted, still table_insert_tuple() should be
> able
> to handle both:
> - the case where this tuple was already toasted.
> - the case where this tuple has been already detoasted.

Yes. That's a current requirement, and any AM that doesn't do that is
already broken (e.g. for INSERT INTO ... SELECT).

Regards,
    Jeff Davis





pgsql-hackers by date:

Previous
From: Jeff Davis
Date:
Subject: Re: RFC: Table access methods and scans
Next
From: Jim Mlodgenski
Date:
Subject: Re: Support for CREATE MODULE?