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 1qxoDr-003bTi-Bt for pgsql-hackers@arkaria.postgresql.org; Tue, 31 Oct 2023 12:51:55 +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 1qxoDq-002Lx7-0y for pgsql-hackers@arkaria.postgresql.org; Tue, 31 Oct 2023 12:51:54 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qxoDp-002Lww-F8 for pgsql-hackers@lists.postgresql.org; Tue, 31 Oct 2023 12:51:53 +0000 Received: from momjian.us ([72.94.173.45]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qxoDm-003Hs4-WA for pgsql-hackers@lists.postgresql.org; Tue, 31 Oct 2023 12:51:52 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=momjian.us; s=2023062407; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:Cc:To:From:Date:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description; bh=t9rAGJlmGOo4fVKBGEa8rRepRTDDts+l9B+BchQnkFE=; b=T94FP hMxAppnx2MLZSOrPO9B3T1diXBQfBFlEmY1Qq4bDcT/zV1mmtsvDWikawKsFMMi/5u77wqG/Vph50 xC0pFq9SwS3rCjnAj1W7dcVIiNbia+rgkz6ofWnKU3AP3Fq6+RssEjSC+yUWh9VwWzrTOqQLoW0vf 09VRw3Q34SQDU5xNjwC1LfkiQmWw4/Gz5x5JPp2xT0JNDjMTRkbz4jVEB3STmkEsyRUIbfxNMa8Uv laLhEbpb2SaulzCQYNZtqzMjxkU8rVbz6+DBZbWpVPg7WGsw74MYMl11hpuvKvJsRv4Y4Yv/m0Sml DgsjsSL48pHuGf7etqr7WbsRRLN8A==; Received: from bruce by momjian.us with local (Exim 4.96) (envelope-from ) id 1qxoDk-0020M0-20; Tue, 31 Oct 2023 08:51:48 -0400 Date: Tue, 31 Oct 2023 08:51:48 -0400 From: Bruce Momjian To: Peter Smith Cc: Michael Paquier , Alvaro Herrera , Tom Lane , PostgreSQL Hackers Subject: Re: [PATCH] postgresql.conf.sample comment alignment. Message-ID: References: <2235495.1659398604@sss.pgh.pa.us> <20220803105804.s6obhhp4qttl4mav@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Thu, Aug 4, 2022 at 12:42:38PM +1000, Peter Smith wrote: > On Thu, Aug 4, 2022 at 11:09 AM Michael Paquier wrote: > > > > On Wed, Aug 03, 2022 at 12:58:04PM +0200, Alvaro Herrera wrote: > > > On 2022-Aug-01, Tom Lane wrote: > > >> One idea for avoiding confusion is to legislate that we won't > > >> use tabs at all in this file (which we could enforce via > > >> .gitattributes, I think). > > > > > > +1. > > > > That's not the first time this 4- or 8-character tab issue is popping > > up around here, so enforcing spaces and having a rule sounds like a > > good idea at the end. > > > > Well, it was only assumed that I had probably confused 4- 8- tabs, but > I don't think I did, so the tabbing issue did not really "pop up" > here. > > e.g. you can see some of the existing alignments I'd suggested > modifying here [1] > - #shared_preload_libraries = '' # (change requires restart) > - #idle_in_transaction_session_timeout = 0 # in milliseconds, 0 is > disable <- (moved comments of the neighbours to keep them all aligned) > - etc. > > I'm not saying replacing the tabs with spaces isn't a good idea - I > also agree probably it is, but that's a different problem to the > alignments I was trying to correct with the patch Patch applied to master. Perhaps someday we will adjust tabs, but for now, this is an improvements. I made a few small adjustments myself. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Only you can decide what is important to you.