Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1to8f4-006gHw-FA for pgsql-committers@arkaria.postgresql.org; Fri, 28 Feb 2025 22:16:51 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1to8f5-000HNX-HC for pgsql-committers@arkaria.postgresql.org; Fri, 28 Feb 2025 22:16:50 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1to8f5-000HNG-A4 for pgsql-committers@lists.postgresql.org; Fri, 28 Feb 2025 22:16:49 +0000 Received: from mail.clear-code.com ([153.126.203.179]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1to8f0-000FJo-2x for pgsql-committers@lists.postgresql.org; Fri, 28 Feb 2025 22:16:48 +0000 Received: from localhost (unknown [IPv6:2404:7a80:9f01:f500:acd0:2aa3:7b08:7206]) by mail.clear-code.com (Postfix) with ESMTPSA id 77FE3685C62; Sat, 1 Mar 2025 07:16:42 +0900 (JST) DKIM-Filter: OpenDKIM Filter v2.11.0 mail.clear-code.com 77FE3685C62 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=clear-code.com; s=default; t=1740781002; bh=mEGaPALa8qhaKhUNqD1+s/x1zOrMpCUQtQBgMZCYJ0U=; h=Date:To:Cc:Subject:From:In-Reply-To:References:From; b=RmOlNgN1hJ9fr+wwxB2elKQZcVuFLUyEzBOc2C63Szu39I1M09dUbnk9Z2FoqbhKC NaEoH8y3iLSrd7jSkc8eRCXt1fLynn/GrsVvz3ljwHHgSmWSNuvTEjtdhGm98sUcNU IqXyF/pujX78lRsAPJ1cU9meXIz6etAlRrfkS3dI= Date: Sat, 01 Mar 2025 07:16:41 +0900 (JST) Message-Id: <20250301.071641.1257013931056303227.kou@clear-code.com> To: sawada.mshk@gmail.com Cc: andrew@dunslane.net, msawada@postgresql.org, pgsql-committers@lists.postgresql.org Subject: Re: pgsql: Refactor COPY FROM to use format callback functions. From: Sutou Kouhei In-Reply-To: References: X-Mailer: Mew version 6.8 on Emacs 30.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 77FE3685C62 X-Rspamd-Server: mail.clear-code.com X-Spamd-Result: default: False [2.90 / 999.00]; SUSPICIOUS_RECIPS(1.50)[]; MID_CONTAINS_FROM(1.00)[]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; FREEMAIL_TO(0.00)[gmail.com]; ARC_NA(0.00)[]; ASN(0.00)[asn:2518, ipnet:2404:7a80::/29, country:JP]; RCVD_COUNT_ZERO(0.00)[0]; TAGGED_RCPT(0.00)[]; FREEMAIL_ENVRCPT(0.00)[gmail.com]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; TO_DN_NONE(0.00)[]; RCPT_COUNT_THREE(0.00)[4] X-Rspamd-Action: no action List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi, Thanks for following up the patch! In "Re: pgsql: Refactor COPY FROM to use format callback functions." on Fri, 28 Feb 2025 12:56:19 -0800, Masahiko Sawada wrote: > Right. I've attached the updated patch. In general, this approach will work but could you keep the same signature for backward compatibility? > --- a/src/backend/commands/copyfromparse.c > +++ b/src/backend/commands/copyfromparse.c > +bool > +NextCopyFromRawFields(CopyFromState cstate, char ***fields, int *nfields, bool is_csv) > +{ > + return NextCopyFromRawFieldsInternal(cstate, fields, nfields, is_csv); > +} NextCopyFromRawFields() uses NextCopyFromRawFields(CopyFromState cstate, char ***fields, int *nfields) (no "bool is_csv") before we remove it. So could you use the no "bool is_csv" signature for backward compatibility? bool NextCopyFromRawFields(CopyFromState cstate, char ***fields, int *nfields) { return NextCopyFromRawFieldsInternal(cstate, fields, nfields, cstate->opts.csv_mode); } > @@ -738,6 +742,15 @@ CopyReadBinaryData(CopyFromState cstate, char *dest, int nbytes) > /* > * Read raw fields in the next line for COPY FROM in text or csv mode. > * Return false if no more lines. > + */ > +bool > +NextCopyFromRawFields(CopyFromState cstate, char ***fields, int *nfields, bool is_csv) > +{ > + return NextCopyFromRawFieldsInternal(cstate, fields, nfields, is_csv); > +} > + > +/* > + * Workhorse for NextCopyFromRawFields(). It may be better that we don't split docs for NextCopyFromRawFields() and NextCopyFromRawFieldsInternal(). How about referring the NextCopyFromRawFieldsInternal() doc from the NextCopyFromRawFields() doc something like the following? /* * See NextCopyFromRawFieldsInternal() for details. */ bool NextCopyFromRawFields(...) { ... } /* * Workhorse for NextCopyFromRawFields(). * * Read raw fields ... * * ... */ static pg_attribute_always_inline bool NextCopyFromRawFieldsInternal() { ... } Thanks, -- kou