diff options
author | Fujii Masao <fujii@postgresql.org> | 2025-04-04 19:32:00 +0900 |
---|---|---|
committer | Fujii Masao <fujii@postgresql.org> | 2025-04-04 19:32:00 +0900 |
commit | 534874fac0b34535c9a5ab9257d6574f78423578 (patch) | |
tree | c92b33bfbd8fa96270cf5215047fb02030c022a6 /src/backend/access/gist/gistscan.c | |
parent | 9ef1851685b718264de47bf543505cf3ec25aaea (diff) | |
download | postgresql-534874fac0b34535c9a5ab9257d6574f78423578.tar.gz postgresql-534874fac0b34535c9a5ab9257d6574f78423578.zip |
Allow "COPY table TO" command to copy rows from materialized views.
Previously, "COPY table TO" command worked only with plain tables and
did not support materialized views, even when they were populated and
had physical storage. To copy rows from materialized views,
"COPY (query) TO" command had to be used, instead.
This commit extends "COPY table TO" to support populated materialized
views directly, improving usability and performance, as "COPY table TO"
is generally faster than "COPY (query) TO". Note that copying from
unpopulated materialized views will still result in an error.
Author: jian he <jian.universality@gmail.com>
Reviewed-by: Kirill Reshke <reshkekirill@gmail.com>
Reviewed-by: David G. Johnston <david.g.johnston@gmail.com>
Reviewed-by: Vignesh C <vignesh21@gmail.com>
Reviewed-by: Fujii Masao <masao.fujii@gmail.com>
Discussion: https://postgr.es/m/CACJufxHVxnyRYy67hiPePNCPwVBMzhTQ6FaL9_Te5On9udG=yg@mail.gmail.com
Diffstat (limited to 'src/backend/access/gist/gistscan.c')
0 files changed, 0 insertions, 0 deletions