Re: Add support for DEFAULT specification in COPY FROM

From: Israel Barth Rubio <barthisrael(at)gmail(dot)com>
To: Zhihong Yu <zyu(at)yugabyte(dot)com>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Add support for DEFAULT specification in COPY FROM
Date: 2022-12-02 14:11:28
Message-ID: CAO_rXXAZHqtto71o6FpE8umXZbCCgQxm20WsBsy=snS9x4yFpw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello all,

I'm submitting a new version of the patch. Instead of changing signature
of several functions in order to use the defaults parameter, it is now
storing
that in the cstate structure, which is already passed to all functions that
were previously modified.

Best regards,
Israel.

Em sex., 7 de out. de 2022 às 17:54, Israel Barth Rubio <
barthisrael(at)gmail(dot)com> escreveu:

> Hello Zhihong,
>
> > For the last question, please take a look at:
> >
> > #define MemSetAligned(start, val, len) \
> >
> > which is called by palloc0().
>
> Oh, I totally missed that. Thanks for the heads up!
>
> I'm attaching the new patch version, which contains both the fix
> to the problem reported by Andres, and removes this useless
> MemSet call.
>
> Best regards,
> Israel.
>

Attachment Content-Type Size
v6-0001-Added-support-for-DEFAULT-in-COPY-FROM.patch application/octet-stream 28.4 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2022-12-02 14:12:04 Re: Error-safe user functions
Previous Message Andrew Dunstan 2022-12-02 14:07:54 Re: initdb: Refactor PG_CMD_PUTS loops