Horton

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

Kirill Reshke <reshkekirill@gmail.com>

View thread View on postgr.es
From: Kirill Reshke <reshkekirill@gmail.com>
To: vignesh C <vignesh21@gmail.com>
Cc: jian he <jian.universality@gmail.com>, Fujii Masao <masao.fujii@oss.nttdata.com>, Andrew Dunstan <andrew@dunslane.net>, "David G. Johnston" <david.g.johnston@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>, Tom Lane <tgl@sss.pgh.pa.us>, Michael Paquier <michael@paquier.xyz>
Date: 2025-04-01T10:18:55Z
Lists: pgsql-hackers 
On Tue, 1 Apr 2025, 11:45 vignesh C, <vignesh21@gmail.com> wrote:

>
> One thing I noticed was that if the materialized view is not refreshed
> user will get stale data
>
> Should we document this?
>


Does this patch alter thus behaviour? User will get stale data even on
HEAD, why should we take a care within this thread?

>

Commits

  1. Allow "COPY table TO" command to copy rows from materialized views.