Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qTSfi-009f7B-6A for pgsql-docs@arkaria.postgresql.org; Tue, 08 Aug 2023 19:47:14 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qTSff-000Ncd-Ge for pgsql-docs@arkaria.postgresql.org; Tue, 08 Aug 2023 19:47:11 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qTSfe-000NcU-TN for pgsql-docs@lists.postgresql.org; Tue, 08 Aug 2023 19:47:11 +0000 Received: from mail-yb1-xb31.google.com ([2607:f8b0:4864:20::b31]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qTSfX-001LPj-Fq for pgsql-docs@lists.postgresql.org; Tue, 08 Aug 2023 19:47:10 +0000 Received: by mail-yb1-xb31.google.com with SMTP id 3f1490d57ef6-d35a9d7a5bdso6052695276.0 for ; Tue, 08 Aug 2023 12:47:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joeconway.com; s=google; t=1691524021; x=1692128821; h=content-transfer-encoding:in-reply-to:subject:from:references:cc:to :content-language:user-agent:mime-version:date:message-id:from:to:cc :subject:date:message-id:reply-to; bh=Q7wfSouQaDImaxsuBCKbKxmp1mzMCs5LH6es30ltggY=; b=mhNFe3s5GnraVr1UG73mjUI+84TnmF4U2zPGfcrUqCDRd4e1+tV16s/p7YktBTMgPv 8OSmMNAxt8iO8055XvnwZqSIHgvrNJ5KH/24oglaVktwQqwECXLOZa9U/2sSKjxIY+vA PxhLR1TILVyJjAG37rZoYNVkrQnH+Wcwp/nPRANcVC9j1aQ+EWE55XwbnhHtYczvLNa1 EppFm2B64XZ2J4nFCmmGpfamAKPhG/gJ3b0S97DPDFt0jXdj2okJYJMRnaQDaLMIkWu+ zb079CZ37RY4P9d0qPKw8GK3nxaBKaeFQ3BLDMMMON49BzPqyt8//PjEodNsvwGN0Vx0 lgRQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1691524021; x=1692128821; h=content-transfer-encoding:in-reply-to:subject:from:references:cc:to :content-language:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=Q7wfSouQaDImaxsuBCKbKxmp1mzMCs5LH6es30ltggY=; b=bWjuQBmeAmCFUl1aDerfXKbBf8WamYhwB1XnxW1twrS71h1ui3Om6g+torUW3lnww7 324oJn4BuF0PZivJmuqMaeBdlKxQobbQUuX3+6RKlEq66zquwbI2irHgaiMBUH/m7Xha ox/27707jpn0GtgkSnt+KznLBZWjm4WEOzV6EQ5oCC8bTB6vdD4W4Cj/Vxw2nYi5pCMT hT55hv5GDTQS9hQVNMizLbEsQBQnOdQMSpqHj6cjZ8+1w/QueZb8c3RnICMMcZla23Lf qik0fAg4oxhA6MCXQ5tDMiYtwE8OTet55ANFUmV/1mtRdSCuiDhjGD/kqgL/2DPuec+n kSXQ== X-Gm-Message-State: AOJu0YwxugwsqQT7rETJZRdT7D/RjqrUJHzUYAMij9JkACboCkx+3Gtn ayhSs01x2X4416Z+fOPcUrmgdg== X-Google-Smtp-Source: AGHT+IGHTyQKxr5jsNQdDCQXMEOpROX9b5fmQbRCamcVGmyh6UHMgC2QbW8Io6LTva+HyzE21D/PzQ== X-Received: by 2002:a25:3606:0:b0:d4c:f456:d55b with SMTP id d6-20020a253606000000b00d4cf456d55bmr586979yba.31.1691524021620; Tue, 08 Aug 2023 12:47:01 -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 v1-20020a2583c1000000b00cb9f38cb782sm2878387ybm.49.2023.08.08.12.47.01 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 08 Aug 2023 12:47:01 -0700 (PDT) Message-ID: <4ccdfd24-e5fc-88a5-ad2e-567042da2b7d@joeconway.com> Date: Tue, 8 Aug 2023 15:47:00 -0400 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.13.0 Content-Language: en-US To: Dan Stoner Cc: pgsql-docs@lists.postgresql.org References: <168675698243.399154.16948504170902857991@wrigleys.postgresql.org> From: Joe Conway Subject: Re: streaming replication depends on matching glibc versions / LOCALE sort order In-Reply-To: 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 8/8/23 15:05, Dan Stoner wrote: > I'm circling back around to this. > > I've cloned the postgresql git repo and started looking thru > doc/src/sgml directory, looking thru the developer FAQ on the wiki, > etc. > > For documentation updates such as this, where would I submit the > patch(es)? Is the process the same as other code commits? > > https://wiki.postgresql.org/wiki/Submitting_a_Patch Yes. Basically send a patch (https://wiki.postgresql.org/wiki/Creating_Clean_Patches) with your changes to the list and register the patch for the next "Open" commitfest: https://commitfest.postgresql.org/ Currently: 2023-09 (Open - 2023-09-01 - 2023-09-30) "Open" means it is open for submission of patches to be considered, and the dates (all of September) are the beginning and end of the commitfest during which the patch would be reviewed, discussed, and hopefully committed. Once the Commitfest is started (2023-09-01) it is no longer Open for new submissions (I forget the exact state name, but it is In-progress or something similar) -- Joe Conway PostgreSQL Contributors Team RDS Open Source Databases Amazon Web Services: https://aws.amazon.com