Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1erhEk-0008R7-0t for pgsql-docs@arkaria.postgresql.org; Fri, 02 Mar 2018 09:44:22 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1erhEi-0005HB-G4 for pgsql-docs@arkaria.postgresql.org; Fri, 02 Mar 2018 09:44:20 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1erhEi-0005Gz-6J for pgsql-docs@lists.postgresql.org; Fri, 02 Mar 2018 09:44:20 +0000 Received: from mail-wm0-x244.google.com ([2a00:1450:400c:c09::244]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1erhEe-0004uH-KQ for pgsql-docs@postgresql.org; Fri, 02 Mar 2018 09:44:19 +0000 Received: by mail-wm0-x244.google.com with SMTP id t3so1939299wmc.2 for ; Fri, 02 Mar 2018 01:44:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=RF9CvcXTHe58Zih5EsJDx/WGXWB0u5ANacTVldUU4BI=; b=DgBcwuPublQlMV5IPSil+GXCgXeE1nYiiWN7x3njRsHG9Yny4nBHYvpzzTQN3mpK8q XG6RSMFXzuTo8Keax7w13TPYgRMxFFs+Zcsaf6zJnCiYLVM7ewzIYEaWjI+EaqvU7+W2 CZHi1cEbUtVjocfqpyga/7PieDmAE6euGyq7UInz/qmqrHdmRi9CNumQHPvTaPip1wrr C6i2u7hE8AUT8PfUboBPSGOyeFnbytZlUVWX+itXxSX+yuQbrtQX/BI3fkwGkjSWhO2q SCrS5yPRywaVWSZ/Q0jenvqs93v/IEUQ8GCEdrUvTSXnkdI8mjV9yCRGLqoryn4swOTY npRQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=RF9CvcXTHe58Zih5EsJDx/WGXWB0u5ANacTVldUU4BI=; b=UFzzLgq39g9JaAqV25o+KX6VoPY/QwtZHmQRAYVjdZ9VsGzWqgJkUPQLP+otKfvaV2 WfQiN+4jSNnUMfsz/HeO4e+BiFLxIRBF72DKo5m59CPnKv6D7iy3oou0/BEpv8aQhhpC D09w+kQZ4pANXZdugivUZ8F1mT3FKr0UL1w7bw+FfKGzxYfyUW6PV6MgCQ74lGMhqFDW ibzoGLx5qsBPu55XCXM75dFx5gI5xs5MBa/NVMSim+xJrZpZ3ZzXPFsZfF5C1Xz6da0C 6txbZ1xcUplN6u0KvyjOmZfuhkr5qdzi5UrsACFxI+TkpYuyPNm2r1k5KPSK2RiN3zCD k0Zw== X-Gm-Message-State: AElRT7G68jQDloQEyII/7uu3ODEiZhbcSwsYUMvbAu6a2mSw+sAde8YF /HfFP14eF7spMLDBNYk0W95Mtg== X-Google-Smtp-Source: AG47ELviLyrBc+KnCk/D75w1EuVry70jhfETJ6cl4yZzafaSKk3C0nm/elkJ9rvG6C8yBOb0cNvPag== X-Received: by 10.28.150.138 with SMTP id y132mr1035673wmd.104.1519983855290; Fri, 02 Mar 2018 01:44:15 -0800 (PST) Received: from [192.168.0.106] (150.123.broadband11.iol.cz. [90.178.123.150]) by smtp.gmail.com with ESMTPSA id l22sm7927831wre.52.2018.03.02.01.44.14 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 02 Mar 2018 01:44:14 -0800 (PST) Subject: Re: libpq options To: Andres Freund , Michael Paquier , Petr Jelinek Cc: sahapasci@gmail.com, pgsql-docs@postgresql.org, Fujii Masao References: <20171122132714.1463.27247@wrigleys.postgresql.org> <20180301093554.qrqgdnfwgs77tj23@alap3.anarazel.de> From: Petr Jelinek Message-ID: Date: Fri, 2 Mar 2018 10:44:13 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <20180301093554.qrqgdnfwgs77tj23@alap3.anarazel.de> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 01/03/18 10:35, Andres Freund wrote: > On 2017-11-25 19:05:54 +0900, Michael Paquier wrote: >> + >> + replication >> + >> + >> + 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 true 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