Re: Allow logical replication to copy tables in binary format
Melih Mutlu <m.melihmutlu@gmail.com>
From: Melih Mutlu <m.melihmutlu@gmail.com>
To: "Takamichi Osumi (Fujitsu)" <osumi.takamichi@fujitsu.com>
Cc: "shiy.fnst@fujitsu.com" <shiy.fnst@fujitsu.com>,
Euler Taveira <euler@eulerto.com>, Amit Kapila <amit.kapila16@gmail.com>,
pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2023-01-12T08:23:09Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Allow logical replication to copy tables in binary format.
- ecb696527c01 16.0 landed
-
Common function for percent placeholder replacement
- c96de2ce1782 16.0 cited
-
Doc: add XML ID attributes to <sectN> and <varlistentry> tags.
- 78ee60ed84bb 16.0 cited
-
Re-order disable_on_error in tab-complete.
- d547f7cf5efc 16.0 cited
-
Make subscription tests pass with log_error_verbosity=verbose
- 19408aae7fa2 15.0 cited
-
Weaken type-OID-matching checks in array_recv and record_recv.
- 670c0a1d474b 14.0 cited
-
Allow logical replication to transfer data in binary format.
- 9de77b545313 14.0 cited
Attachments
- v6-0001-Allow-logical-replication-to-copy-table-in-binary.patch (application/octet-stream) patch v6-0001
Hi, Thanks for your reviews. Takamichi Osumi (Fujitsu) <osumi.takamichi@fujitsu.com>, 12 Oca 2023 Per, 06:07 tarihinde şunu yazdı: > On Wednesday, January 11, 2023 7:45 PM Melih Mutlu <m.melihmutlu@gmail.com> > wrote: > (1-1) There is no need to log the version and the query by elog here. > (1-2) Also, I suggest we can remove the server_version variable itself, > because we have only one actual reference for it. > There is a style that we call walrcv_server_version in the > 'if condition' directly like existing codes in > fetch_remote_table_info(). > (1-3) Suggestion to improve comments. > FROM: > /* If the publisher is v16 or later, copy in binary format.*/ > TO: > /* If the publisher is v16 or later, copy data in the required data > format. */ > Forgot to remove that LOG line. Removed it now and applied other suggestions too. > I think if we change the order of this part of check like below, then > it would look more aligned with other existing test codes introduced by > this patch. > Right. Changed it to make it more aligned with the rest. Thanks, -- Melih Mutlu Microsoft