Re: POC PATCH: copy from ... exceptions to: (was Re: VLDB Features)

From: Andrei Lepikhov <a(dot)lepikhov(at)postgrespro(dot)ru>
To: Damir Belyalov <dam(dot)bel07(at)gmail(dot)com>, zhihuifan1213(at)163(dot)com
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Daniel Gustafsson <daniel(at)yesql(dot)se>, torikoshia <torikoshia(at)oss(dot)nttdata(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de>, anisimow(dot)d(at)gmail(dot)com, HukuToc(at)gmail(dot)com, Alena Rybakina <lena(dot)ribackina(at)yandex(dot)ru>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: POC PATCH: copy from ... exceptions to: (was Re: VLDB Features)
Date: 2023-11-24 03:52:25
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On 14/11/2023 17:10, Damir Belyalov wrote:
>  Here is a very straw-man-level sketch of what I think might work.
>  The option to COPY FROM looks something like
>       ERRORS TO other_table_name (item [, item [, ...]])
> I tried to implement the patch using a table and came across a number of
> questions.
> Which table should we implement for this feature: a system catalog table
> or store this table as a file or create a new table?
> In these cases, security and user rights management issues arise.
> It is better for other users not to see error lines from another user.
> It is also not clear how access rights to this table are inherited and
> be given.

Previous reviews have given helpful ideas about storing errors in the
new table.
It should be trivial code - use the current table name + 'err' + suffix
as we already do in the case of conflicting auto-generated index names.
The 'errors table' must inherit any right policies from the table, to
which we do the copy.

Andrei Lepikhov
Postgres Professional

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2023-11-24 04:06:25 Don't use bms_membership in places where it's not needed
Previous Message Zhijie Hou (Fujitsu) 2023-11-24 03:35:02 RE: Synchronizing slots from primary to standby