| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
| Cc: | Luis Carril <luis(dot)carril(at)swarm64(dot)com>, Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>, PG Bug reporting form <noreply(at)postgresql(dot)org>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
| Subject: | Re: BUG #15552: Unexpected error in COPY to a foreign table in a transaction |
| Date: | 2018-12-19 03:51:57 |
| Message-ID: | 20181219035157.GB6577@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Wed, Dec 19, 2018 at 11:52:09AM +0900, Amit Langote wrote:
> Hmm, note that we don't pass CopyState->freeze option to the FDW drivers
> today, though we may in the future when we add an *actual* COPY interface
> to FDWs. Wouldn't it be a good idea to prevent specifying the FREEZE
> option for foreign tables as COPY targets until then? Of course, that's
> something for -hackers to consider.
No idea if that will happen. One argument for doing nothing yet is that
this command does not fail now so changing it may cause compatibility
problems.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Langote | 2018-12-19 04:01:01 | Re: BUG #15552: Unexpected error in COPY to a foreign table in a transaction |
| Previous Message | Amit Langote | 2018-12-19 02:52:09 | Re: BUG #15552: Unexpected error in COPY to a foreign table in a transaction |