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 3bee08c2ca0fab15d14899afcb19490f29e0ec6f.camel@j-davis.com
Whole thread Raw
In response to Re: alter table set TABLE ACCESS METHOD  (Justin Pryzby <pryzby@telsasoft.com>)
Responses Re: alter table set TABLE ACCESS METHOD  (Jeff Davis <pgsql@j-davis.com>)
List pgsql-hackers
On Thu, 2021-05-06 at 17:19 -0500, Justin Pryzby wrote:
> If ATRewriteTable didn't
> handle this,
> data would become inaccessible if an AM failed to de-toast tuples.

If the AM fails to detoast tuples, it's got bigger problems than ALTER
TABLE. What about INSERT INTO ... SELECT?

It's the table AM's responsibility to detoast out-of-line datums and
toast any values that are too large (see
heapam.c:heap_prepare_insert()).

Regards,
    Jeff Davis





pgsql-hackers by date:

Previous
From: Chapman Flack
Date:
Subject: Re: pg_upgrade not preserving comments on predefined roles
Next
From: Masahiko Sawada
Date:
Subject: Re: Replication slot stats misgivings