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 1qCfv4-0001oQ-O5 for pgsql-docs@arkaria.postgresql.org; Fri, 23 Jun 2023 12:29:42 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1qCfu5-0001iO-5M for pgsql-docs@arkaria.postgresql.org; Fri, 23 Jun 2023 12:28:41 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qCfu4-0001hX-Dj for pgsql-docs@lists.postgresql.org; Fri, 23 Jun 2023 12:28:40 +0000 Received: from mail-yb1-xb35.google.com ([2607:f8b0:4864:20::b35]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qCfu1-0000L9-Fk for pgsql-docs@lists.postgresql.org; Fri, 23 Jun 2023 12:28:38 +0000 Received: by mail-yb1-xb35.google.com with SMTP id 3f1490d57ef6-bff0beb2d82so485737276.2 for ; Fri, 23 Jun 2023 05:28:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joeconway.com; s=google; t=1687523316; x=1690115316; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=47oeabK6wqjjOWDD0auxj8vOiBFVFIh46E5jXkfcHos=; b=RWESGKzXqM5LcLVpuqAPk+zqXWUS0EAB1pSLppSNPLeiOmjT8uldbn7npIttZnidmA OFQz1dN5Ew68/9ig+Om5tPPelZCIzFhKUDyzBm3Hz01/weKa6fh7qCb9eEaRguzdlJYl yFqnv+QcF3yjuIJS2Pru+p6uXYUy8q214mmi1VtD53ROTWbvQ7ILP97r0t44FeE7HZ0n mIKAjYiVhfQDfjJ1wVkaNjUmVkWXlYEFEsVyXsY/NAc85DRSDJjMCSeWCb2zLim520Vp 2q9RNGchGpqSrRyyfct07/R7M12cXEv74de9tyGWMtggsu6dtlDtNvZydVRuzm27284A T4JA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1687523316; x=1690115316; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=47oeabK6wqjjOWDD0auxj8vOiBFVFIh46E5jXkfcHos=; b=VbheoctUMdie8QsS807VYtqhSTTb2H3OiQwApPPEUOfsffPmlK0sLI7KUgVGipXUyU ABYsx8DrySElafF+I9Wrw7MyA+vRN3R8EpwJPc5ZJv59Iroc8BUFeN8SxP8tMFLA6ZL5 +DdQPfSV/tT1t08RVcZ0d7KH2xNGlg0GlZSvRAhXbrtMRxbiXt8qRlRNujPboiiVc3zL 643fhqH8m30SIQmAGL7AiJhw91uDDPPM6yPzrRf/iHDy9oOgePDRqyg60EuWRxR6l8bg 6h8pktI+uGsaE0bqfAyTLIaR5+kW7VgzVykkFBnk3MoY53p0OorC/VFhC4SbpjSN2kyE F/Bw== X-Gm-Message-State: AC+VfDzq+GiKFyGFFc/7MEUzk7aDSslHp+b2GQi6C3JhsvIHexKOVORf 25DOUvUSZpuzRo8HdQ5du80Ilg== X-Google-Smtp-Source: ACHHUZ4okFuCQZWOOdJk0r2IeZwUN7A3rL/ZHPhjd+D6H/pSiKRoSxEnLVAFSz4FnFnKo+Iz1OICQA== X-Received: by 2002:a25:cec3:0:b0:bcd:39d6:1ab1 with SMTP id x186-20020a25cec3000000b00bcd39d61ab1mr17119469ybe.39.1687523316620; Fri, 23 Jun 2023 05:28:36 -0700 (PDT) Received: from [192.168.4.41] (162-239-31-113.lightspeed.dybhfl.sbcglobal.net. [162.239.31.113]) by smtp.gmail.com with ESMTPSA id e63-20020a256942000000b00bc41075297fsm2039452ybc.23.2023.06.23.05.28.35 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 23 Jun 2023 05:28:36 -0700 (PDT) Message-ID: Date: Fri, 23 Jun 2023 08:28:35 -0400 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.11.0 Subject: Re: streaming replication depends on matching glibc versions / LOCALE sort order Content-Language: en-US To: danstoner@gmail.com, pgsql-docs@lists.postgresql.org References: <168675698243.399154.16948504170902857991@wrigleys.postgresql.org> From: Joe Conway In-Reply-To: <168675698243.399154.16948504170902857991@wrigleys.postgresql.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 6/14/23 11:36, PG Doc comments form wrote: > In Slack, it seems clear that this is a "well known issue" to some people on > the project, but it continues to burn people in the wild. > > This seems important enough that it should be included in the official > docs. > > Can I do anything to help get the documentation updated? Absolutely! If you can suggest which doc sections should be altered and proposed wording, that would be a great start. Bonus points if you send it in as a patch against the corresponding sgml files. Note, I recently gave a talk on the subject -- feel free to get examples, etc from the slides: https://www.joeconway.com/presentations/glibc_issues-PGCon-2023.pdf I can also help with wordsmithing and committing the changes once we have them fully baked. -- Joe Conway PostgreSQL Contributors Team RDS Open Source Databases Amazon Web Services: https://aws.amazon.com