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.
--
regards,
Andrei Lepikhov
Postgres Professional
