Re: in BeginCopyTo make materialized view using COPY TO instead of COPY (query).

From: newtglobal postgresql_contributors <postgresql_contributors(at)newtglobalcorp(dot)com>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org
Cc: Jian He <hejian(dot)mark(at)gmail(dot)com>
Subject: Re: in BeginCopyTo make materialized view using COPY TO instead of COPY (query).
Date: 2025-03-13 06:50:31
Message-ID: 174184863169.294107.2193231434852582080.pgcf@coridan.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

The following review has been posted through the commitfest application:
make installcheck-world: not tested
Implements feature: not tested
Spec compliant: not tested
Documentation: not tested

Hi,
Tested the latest patch that allows direct `COPY` operations on Materialized Views, removing the need for `COPY (SELECT ...)`. This enhancement reduces query overhead, improving performance by **4–5%**.
Example:
Previous approach:
COPY (SELECT * FROM staff_summary) TO STDOUT WITH CSV HEADER;
Optimized approach:
COPY staff_summary TO STDOUT WITH CSV HEADER;
Performance tests were conducted using a Materialized View containing around 80,000 records, confirming that the new approach is faster and more efficient for exporting data.

Regards,
Newt Global PostgreSQL Contributors

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message newtglobal postgresql_contributors 2025-03-13 06:51:40 Re: Add XMLNamespaces to XMLElement
Previous Message Ajin Cherian 2025-03-13 06:49:16 Re: Proposal: Filter irrelevant change before reassemble transactions during logical decoding