Re: Add header support to text format and matching feature

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: Daniel Verite <daniel(at)manitou-mail(dot)org>, Julien Rouhaud <rjuju123(at)gmail(dot)com>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Greg Stark <stark(at)mit(dot)edu>, Rémi Lapeyre <remi(dot)lapeyre(at)lenstra(dot)fr>, Zhihong Yu <zyu(at)yugabyte(dot)com>, David Steele <david(at)pgmasters(dot)net>, vignesh C <vignesh21(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Add header support to text format and matching feature
Date: 2022-06-16 07:24:56
Message-ID: 182b63dd-efa6-a108-4c28-fd5104518d01@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 15.06.22 13:50, Daniel Verite wrote:
> The other errors in the list above are more about the format itself,
> with options that make sense only for one format. So the way we're
> supposed to understand ERRCODE_FEATURE_NOT_SUPPORTED in these
> other cases is that such format does not support such feature,
> but without implying that it's a limitation.

I don't feel very strongly about this. It makes sense to stay
consistent with the existing COPY code.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2022-06-16 07:25:36 Re: Skipping logical replication transactions on subscriber side
Previous Message Amit Langote 2022-06-16 07:00:23 Re: Replica Identity check of partition table on subscriber