Re: COPY TO (FREEZE)?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, rjuju123(at)gmail(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: COPY TO (FREEZE)?
Date: 2023-10-29 01:54:05
Message-ID: 2029289.1698544445@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian <bruce(at)momjian(dot)us> writes:
> On Sat, Oct 28, 2023 at 09:39:53PM -0400, Tom Lane wrote:
>> Not thrilled by the wording here.

> I think it is modeled after:

> errmsg("COPY force null only available using COPY FROM")));

Well, now that you bring it up, that's no sterling example of
clear writing either. Maybe change that while we're at it,
say to "FORCE NULL option must not be used in COPY TO"?
(Also, has it got the right ERRCODE?)

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2023-10-29 02:03:59 Re: COPY TO (FREEZE)?
Previous Message Bruce Momjian 2023-10-29 01:47:03 Re: COPY TO (FREEZE)?