| From: | "Euler Taveira" <euler(at)eulerto(dot)com> |
|---|---|
| To: | "Amit Kapila" <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | "Melih Mutlu" <m(dot)melihmutlu(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Allow logical replication to copy tables in binary format |
| Date: | 2022-08-11 13:26:40 |
| Message-ID: | 7cf14e66-8cea-406f-9607-607a397292f6@www.fastmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Aug 11, 2022, at 8:04 AM, Amit Kapila wrote:
> On Thu, Aug 11, 2022 at 7:34 AM Euler Taveira <euler(at)eulerto(dot)com> wrote:
> >
> > The reason to use text format is that it is error prone. There are restrictions
> > while using the binary format. For example, if your schema has different data
> > types for a certain column, the copy will fail.
> >
>
> Won't such restrictions hold true even during replication?
I expect that the COPY code matches the proto.c code. The point is that table
sync is decoupled from the logical replication. Hence, we should emphasize in
the documentation that the restrictions *also* apply to the initial table
synchronization.
--
Euler Taveira
EDB https://www.enterprisedb.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Melih Mutlu | 2022-08-11 13:46:21 | Re: Allow logical replication to copy tables in binary format |
| Previous Message | Ranier Vilela | 2022-08-11 12:52:49 | Use array as object (src/fe_utils/parallel_slot.c) |