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

From: Kirill Reshke <reshkekirill(at)gmail(dot)com>
To: vignesh C <vignesh21(at)gmail(dot)com>
Cc: jian he <jian(dot)universality(at)gmail(dot)com>, Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Michael Paquier <michael(at)paquier(dot)xyz>
Subject: Re: in BeginCopyTo make materialized view using COPY TO instead of COPY (query).
Date: 2025-04-01 10:18:55
Message-ID: CALdSSPiNtJMQFhSWSJnkwqwTkDAe3nqTjZ2yqs9jZVC6SYh6FA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, 1 Apr 2025, 11:45 vignesh C, <vignesh21(at)gmail(dot)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?

>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2025-04-01 10:32:34 Re: [PATCH] Fix build on MINGW on ARM64
Previous Message Pavel Stehule 2025-04-01 10:15:30 Re: Add partial :-variable expansion to psql \copy