diff options
author | Michael Paquier <michael@paquier.xyz> | 2021-07-28 10:10:44 +0900 |
---|---|---|
committer | Michael Paquier <michael@paquier.xyz> | 2021-07-28 10:10:44 +0900 |
commit | b0483263dda0824cc49e3f8a022dab07e1cdf9a7 (patch) | |
tree | e9aa48baf7b4159eae107a8a3cfb613927f9a854 /src/backend/jit/llvm/llvmjit_expr.c | |
parent | 4b763ff642e1a3608cbcaff062f6c2f465bfc6bd (diff) | |
download | postgresql-b0483263dda0824cc49e3f8a022dab07e1cdf9a7.tar.gz postgresql-b0483263dda0824cc49e3f8a022dab07e1cdf9a7.zip |
Add support for SET ACCESS METHOD in ALTER TABLE
The logic used to support a change of access method for a table is
similar to changes for tablespace or relation persistence, requiring a
table rewrite with an exclusive lock of the relation changed. Table
rewrites done in ALTER TABLE already go through the table AM layer when
scanning tuples from the old relation and inserting them into the new
one, making this implementation straight-forward.
Note that partitioned tables are not supported as these have no access
methods defined.
Author: Justin Pryzby, Jeff Davis
Reviewed-by: Michael Paquier, Vignesh C
Discussion: https://postgr.es/m/20210228222530.GD20769@telsasoft.com
Diffstat (limited to 'src/backend/jit/llvm/llvmjit_expr.c')
0 files changed, 0 insertions, 0 deletions