Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jsrfn-0005Ys-OV for pgsql-hackers@arkaria.postgresql.org; Tue, 07 Jul 2020 17:46:27 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jsrfm-0003N6-M6 for pgsql-hackers@arkaria.postgresql.org; Tue, 07 Jul 2020 17:46:26 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jsrfm-0003Mx-FG for pgsql-hackers@lists.postgresql.org; Tue, 07 Jul 2020 17:46:26 +0000 Received: from mail-qv1-xf44.google.com ([2607:f8b0:4864:20::f44]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1jsrfi-0005UL-2W for pgsql-hackers@postgresql.org; Tue, 07 Jul 2020 17:46:26 +0000 Received: by mail-qv1-xf44.google.com with SMTP id di5so14275768qvb.11 for ; Tue, 07 Jul 2020 10:46:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=4D/3eTQNo0eyY2WWI0f4hyuSpoEaDLBzlOWDJ8iUvis=; b=KkSkZOHBqLuoR4e/lwx0sqUkypM2Zq4+umm9EuSlrqXE2BkgO0CS4pW+3YXOyK9dNy OHfrJkMLqPzcCB9AXzIjHji0/11GXk/WAo9AbRw1FVUE3QVXUObYOhSk7KRmpItiAHu9 L6if3dNZltEi17sgztwsxK3TeA6T1PO46+QcD9doyLAbLBIkKvHzENa5kW+gzmxxu7/c sh1lCmtQILwZUTSyZ0zIVbyRLE5K7/nKR3PnP0ajmmniCNv/b85itGkoE2tNzUPW7jcc jYCSd1o2cUYtBJkWoY1XyK6zKgd8ohsa7vIw+Y+Aap/chWZ04qyhkX35ykBCawKPI+NT /9uQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=4D/3eTQNo0eyY2WWI0f4hyuSpoEaDLBzlOWDJ8iUvis=; b=S31eFf4Eue3yifrQaLT5994Ws0BaNibL5dtYHQlRbtCnd/LhoY0syPfs3SnlcMlQ95 E1fkeMt/i04J8kzjc4/sWtFYcAEt7GJeBPfiJLtGKsvebdHkRTTvCCpy8Ic/3SPjUDr/ WgY7jR4vWZZT9luxXEGaFyc1FlTYwI8uN395BCASEbxo8wmQ0f6KoEM89lOnFJEZKh7M jyge3OL8mjxFe8MBrdBtV5YtqzyNd3waxSzfrbA46PhbucVOMAd6Jlz37OWfcJs67jYM xuGY45J5z0G7srSxMktZ1IgI4+awdmofidMFLiuftG3EE8H3XUn21s68UIIXyNlPn3qe h/kA== X-Gm-Message-State: AOAM530v3ECRnA8pPcLXjS4nS/ILvlweCMYiN2lvvr0slJ92JtVpQewD 0Liu8NYotOGnsBCgNKg6mk+utw== X-Google-Smtp-Source: ABdhPJy4aJ+4rsFVHJWyKTmWqZhSI8K2E9szHoIZJDTNhXdtHDRpNcXrH1V5SmQbxD5o0sF82eBvyw== X-Received: by 2002:a05:6214:8f4:: with SMTP id dr20mr50203586qvb.228.1594143980333; Tue, 07 Jul 2020 10:46:20 -0700 (PDT) Received: from perhan.alvh.no-ip.org ([190.95.18.252]) by smtp.gmail.com with ESMTPSA id n64sm24477512qke.77.2020.07.07.10.46.19 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 07 Jul 2020 10:46:19 -0700 (PDT) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id E215F2A3DFE; Tue, 7 Jul 2020 13:46:17 -0400 (-04) Date: Tue, 7 Jul 2020 13:46:17 -0400 From: Alvaro Herrera To: Andres Freund Cc: Robert Haas , Stephen Frost , Kyotaro Horiguchi , Michael Paquier , "Jonathan S. Katz" , Dave Cramer , Fujii Masao , Masahiko Sawada , Vladimir Sitnikov , "pgsql-hackers@postgresql.org" , Peter Geoghegan Subject: Re: SIGSEGV from START_REPLICATION 0/XXXXXXX in XLogSendPhysical () at walsender.c:2762 Message-ID: <20200707174617.GA18867@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20200624195239.n3c33txha6mtvxku@alap3.anarazel.de> User-Agent: Mutt/1.10.1 (2018-07-13) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2020-Jun-24, Andres Freund wrote: > As I said before, I've utilized being able to do both over a single > connection (among others to initialize a logical replica using a base > backup). And I've seen at least one other codebase (developed without my > input) doing so. I really don't understand how you just dismiss this > without any sort of actual argument. Yes, those uses can be fixed to > reconnect with a different replication parameter, but that's code that > needs to be adjusted and it requires adjustments to pg_hba.conf etc. > > And obviously you'd lock out older versions of jdbc, and possibly other > drivers. Well, I had understood that you were talking from a hypothetical position, not that you were already using the thing that way. After these arguments, I agree to leave things alone, and nobody else seems to be arguing in that direction, so I'll mark the open item as closed. Thanks, -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services