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

From: jian he <jian(dot)universality(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: in BeginCopyTo make materialized view using COPY TO instead of COPY (query).
Date: 2025-01-06 09:34:43
Message-ID: CACJufxGZgh4oNV_8TqBwRoL+WFB2n3EqN97aMcuEmjuG+qm0qw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message 赵宇鹏 (宇彭) 2025-01-06 09:41:49 Temporary Views Cleanup Issue
Previous Message wenhui qiu 2025-01-06 08:53:43 Re: [RFC] Lock-free XLog Reservation from WAL