Re: in BeginCopyTo make materialized view using COPY TO instead of COPY (query).
jian he <jian.universality@gmail.com>
From: jian he <jian.universality@gmail.com>
To: PostgreSQL-development <pgsql-hackers@postgresql.org>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Michael Paquier <michael@paquier.xyz>
Date: 2025-01-28T02:48:25Z
Lists: pgsql-hackers
Attachments
- v1-0001-COPY-materialized_view-TO.patch (text/x-patch) patch v1-0001
On Mon, Jan 6, 2025 at 5:34 PM jian he <jian.universality@gmail.com> wrote: > > hi. > > about this issue, > last email in 2012 (https://postgr.es/m/8967.1353167301@sss.pgh.pa.us) > """ > Even if it happens to be trivial in the current patch, it's an added > functional requirement that we might later regret having cavalierly > signed up for. And, as noted upthread, relations that support only > one direction of COPY don't exist at the moment; that would be adding > an asymmetry that we might later regret, too. > > regards, tom lane > """ > > but now we have numerous COPY options that work solely in a single > direction of COPY. > I think now we can make some kind of relation (pg_class.relkind) that > only works in one direction of COPY. hi. patch attached. also cc to Tom, since at that time, you are against the idea of ``COPY matview TO``.
Commits
-
Allow "COPY table TO" command to copy rows from materialized views.
- 534874fac0b3 18.0 landed