| From: | Petr Jelinek <petr(dot)jelinek(at)2ndquadrant(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Petr Jelinek <petr(at)2ndquadrant(dot)com> |
| Cc: | sahapasci(at)gmail(dot)com, pgsql-docs(at)postgresql(dot)org, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
| Subject: | Re: libpq options |
| Date: | 2018-03-02 09:44:13 |
| Message-ID: | e2c073c5-8ed6-5cdb-e390-678a2026a4f1@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On 01/03/18 10:35, Andres Freund wrote:
> On 2017-11-25 19:05:54 +0900, Michael Paquier wrote:
>> + <varlistentry id="libpq-connect-replication" xreflabel="replication">
>> + <term><literal>replication</literal></term>
>> + <listitem>
>> + <para>
>> + This option determines if a backend should use the replication
>> + protocol.
>
> "should"? The backend will, and the client will have to do so as well.
>
I think so as well.
>
>> A Boolean value of <literal>true</literal> tells the backend
>> + to go into walsender mode, wherein a small set of replication commands
>> + can be issued instead of SQL statements.
>
> This actually is wrong now I think. Petr?
>
If the replication is true, we don't have database connection so only
replication commands can be executed.
SQL commands work when replication is set to database.
--
Petr Jelinek http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2018-03-02 11:58:50 | Re: libpq options |
| Previous Message | Greg k | 2018-03-02 06:04:42 | Postgres 10 and the pg_ctl "--wait" option |