Content-Type: multipart/alternative;
 boundary="------------fD9OltZetOFm0FcTMOJ0z6CA"
Message-ID: <2c18cf9c-b895-4d98-a700-fbf12463a984@yandex.ru>
Date: Tue, 14 Nov 2023 13:16:35 +0300
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: POC PATCH: copy from ... exceptions to: (was Re: VLDB Features)
To: Damir Belyalov <dam.bel07@gmail.com>, zhihuifan1213@163.com
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Daniel Gustafsson <daniel@yesql.se>,
 torikoshia <torikoshia@oss.nttdata.com>,
 PostgreSQL Hackers <pgsql-hackers@postgresql.org>,
 Andres Freund <andres@anarazel.de>, anisimow.d@gmail.com, HukuToc@gmail.com,
 Andrey Lepikhov <a.lepikhov@postgrespro.ru>,
 pgsql-hackers@lists.postgresql.org
References: <483E1B59-4A80-450B-8685-7CC12762FD5A@anarazel.de>
 <9a94e684d6528dff74de5959e97032f3@oss.nttdata.com>
 <8e5c596e47435e3b37b7a751ebcd9569@oss.nttdata.com>
 <20230322175000.qbdctk7bnmifh5an@awork3.anarazel.de>
 <16e09747fcfbb21c30e4c1009c416aa4@oss.nttdata.com>
 <19551e8c2717c24689913083f841ddb5@oss.nttdata.com>
 <CALH1LguOY-VvJBWvjpLR2W3t0Z2p=LGSK5tzLrKwtzZ2UsqwGg@mail.gmail.com>
 <43399b33fe573f0548410893f41f84b6@oss.nttdata.com>
 <CALH1LgseNT7mxpGzQsQwOJz_UwYBo6L-4vR9tmJqb-WNPkt6Bg@mail.gmail.com>
 <8de9d5e1-2f81-ee2e-ece4-b1a6ede1f285@yandex.ru>
 <b74c1c3e3cc1c5d7ad5fb527b27d2b60@oss.nttdata.com>
 <c0fb57b82b150953f26a5c7e340412e8@oss.nttdata.com>
 <CALH1Lgtg39crESw644KDH+ejBWuW3Vospe67F-ZWXNeBMEE=PA@mail.gmail.com>
 <58fa3b63e88ffd0a09273e38aec0661e@oss.nttdat!>
 <B082C6BE-D2F2-4DD4-8649-E81E24A6840E@yesql.se>
 <752672.1699474336@sss.pgh.pa.us> <878r77mtlt.fsf@163.com>
 <CALH1LgueaSXWJ=eZ-0-LYCm8tF45SoOM0QFc55C-xpbGfNkFyg@mail.gmail.com>
Content-Language: en-US
From: Alena Rybakina <lena.ribackina@yandex.ru>
In-Reply-To: <CALH1LgueaSXWJ=eZ-0-LYCm8tF45SoOM0QFc55C-xpbGfNkFyg@mail.gmail.com>
Archived-At: <https://www.postgresql.org/message-id/2c18cf9c-b895-4d98-a700-fbf12463a984%40yandex.ru>
Precedence: bulk

This is a multi-part message in MIME format.
--------------fD9OltZetOFm0FcTMOJ0z6CA
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

Hi!

On 14.11.2023 13: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.
>
>
Maybe we can add a guc or a parameter to output such errors during the 
execution of the copy function with errors and check whether the user 
has enough rights to set such a parameter?

That is, I propose to give the user a choice to run copy with and 
without saving errors and at the same time immediately check whether the 
option with error output is possible for him in principle?

-- 
Regards,
Alena Rybakina

--------------fD9OltZetOFm0FcTMOJ0z6CA
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>Hi!<br>
    </p>
    <div class="moz-cite-prefix">On 14.11.2023 13:10, Damir Belyalov
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CALH1LgueaSXWJ=eZ-0-LYCm8tF45SoOM0QFc55C-xpbGfNkFyg@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">
        <div class="gmail_quote">
          <blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> Here
            is a very straw-man-level sketch of what I think might work.<br>
             The option to COPY FROM looks something like<br>
            <br>
                  ERRORS TO other_table_name (item [, item [, ...]])<br>
          </blockquote>
          <div><br>
          </div>
          <div>I tried to implement the patch using a table and came
            across a number of questions.<br>
            <br>
            Which table should we implement for this feature: a system
            catalog table or store this table as a file or create a new
            table?<br>
            <br>
            In these cases, security and user rights management issues
            arise.</div>
          <div>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.</div>
          <div><br>
          </div>
          <br>
        </div>
      </div>
    </blockquote>
    <p>Maybe we can add a guc or a parameter to output such errors
      during the execution of the copy function with errors and check
      whether the user has enough rights to set such a parameter?</p>
    <p>That is, I propose to give the user a choice to run copy with and
      without saving errors and at the same time immediately check
      whether the option with error output is possible for him in
      principle?<br>
    </p>
    <pre class="moz-signature" cols="72">-- 
Regards,
Alena Rybakina</pre>
  </body>
</html>

--------------fD9OltZetOFm0FcTMOJ0z6CA--