@@ -236,8 +236,9 @@ ____________________________________________________________________________-->
236
236
<listitem>
237
237
<para>
238
238
The value of this parameter overrides the
239
- <xref linkend="guc-synchronous-commit"/> setting. The default
240
- value is <literal>off</literal>.
239
+ <xref linkend="guc-synchronous-commit"/> setting within this
240
+ subscription's apply worker processes. The default value
241
+ is <literal>off</literal>.
241
242
</para>
242
243
243
244
<para>
@@ -262,6 +263,27 @@ ____________________________________________________________________________-->
262
263
</listitem>
263
264
</varlistentry>
264
265
266
+ <varlistentry>
267
+ <term><literal>binary</literal> (<type>boolean</type>)</term>
268
+ <listitem>
269
+ <para>
270
+ Specifies whether the subscription will request the publisher to
271
+ send the data in binary format (as opposed to text).
272
+ The default is <literal>false</literal>.
273
+ Even when this option is enabled, only data types that have
274
+ binary send and receive functions will be transferred in binary.
275
+ </para>
276
+
277
+ <para>
278
+ When doing cross-version replication, it could happen that the
279
+ publisher has a binary send function for some data type, but the
280
+ subscriber lacks a binary receive function for the type. In
281
+ such a case, data transfer will fail, and
282
+ the <literal>binary</literal> option cannot be used.
283
+ </para>
284
+ </listitem>
285
+ </varlistentry>
286
+
265
287
<varlistentry>
266
288
<term><literal>connect</literal> (<type>boolean</type>)</term>
267
289
<listitem>
@@ -290,6 +312,17 @@ ____________________________________________________________________________-->
290
312
</para>
291
313
</listitem>
292
314
</varlistentry>
315
+ <varlistentry>
316
+ <term><literal>streaming</literal> (<type>boolean</type>)</term>
317
+ <listitem>
318
+ <para>
319
+ Specifies whether streaming of in-progress transactions should
320
+ be enabled for this subscription. By default, all transactions
321
+ are fully decoded on the publisher, and only then sent to the
322
+ subscriber as a whole.
323
+ </para>
324
+ </listitem>
325
+ </varlistentry>
293
326
</variablelist></para>
294
327
____________________________________________________________________________-->
295
328
<para>
@@ -345,7 +378,7 @@ ____________________________________________________________________________-->
345
378
<term><literal>synchronous_commit</literal> (<type>enum</type>)</term>
346
379
<listitem>
347
380
<para>
348
- 该参数的值会覆盖<xref linkend="guc-synchronous-commit"/>设置。
381
+ 在这个订阅的应用worker进程时, 该参数的值会覆盖<xref linkend="guc-synchronous-commit"/>设置。
349
382
默认值是<literal>off</literal>。
350
383
</para>
351
384
@@ -366,6 +399,22 @@ ____________________________________________________________________________-->
366
399
</listitem>
367
400
</varlistentry>
368
401
402
+ <varlistentry>
403
+ <term><literal>binary</literal> (<type>boolean</type>)</term>
404
+ <listitem>
405
+ <para>
406
+ 指定订阅是否要求发布器以二进制格式(相对的是文本格式)发送数据。
407
+ 默认值是<literal>false</literal>。
408
+ 即使此选项被启用,也只有具备二进制发送和接收函数的数据类型将以二进制传输。
409
+ </para>
410
+
411
+ <para>
412
+ 在进行跨版本复制时,可能会出现发布器具有某些数据类型的二进制发送函数,但订阅器缺乏针对此类型的二进制接收函数的情况。
413
+ 在这种情况下,数据传输将失败,并且<literal>binary</literal>选项不能被使用。
414
+ </para>
415
+ </listitem>
416
+ </varlistentry>
417
+
369
418
<varlistentry>
370
419
<term><literal>connect</literal> (<type>boolean</type>)</term>
371
420
<listitem>
@@ -388,8 +437,16 @@ ____________________________________________________________________________-->
388
437
</para>
389
438
</listitem>
390
439
</varlistentry>
391
- </variablelist>
392
- </para>
440
+ <varlistentry>
441
+ <term><literal>streaming</literal> (<type>boolean</type>)</term>
442
+ <listitem>
443
+ <para>
444
+ 指定是否对此订阅启用进行中事务的流。
445
+ 默认情况下,所有事务都在发布器上完全解码,直到那时才作为整体发送给订阅器。
446
+ </para>
447
+ </listitem>
448
+ </varlistentry>
449
+ </variablelist></para>
393
450
</listitem>
394
451
</varlistentry>
395
452
</variablelist>
0 commit comments