Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hpEmt-0006ru-3d for pgsql-hackers@arkaria.postgresql.org; Sun, 21 Jul 2019 16:34:15 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hpEmr-0002KY-PJ for pgsql-hackers@arkaria.postgresql.org; Sun, 21 Jul 2019 16:34:13 +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_SHA1:256) (Exim 4.89) (envelope-from ) id 1hpEmr-0002KR-Gp for pgsql-hackers@lists.postgresql.org; Sun, 21 Jul 2019 16:34:13 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hpEmq-00056F-6B for pgsql-hackers@postgresql.org; Sun, 21 Jul 2019 16:34:13 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id x6LGY5uD017732; Sun, 21 Jul 2019 12:34:05 -0400 From: Tom Lane To: Alexander Lakhin cc: pgsql-hackers@postgresql.org, Michael Paquier Subject: Re: Fix typos and inconsistencies for HEAD (take 7) In-reply-to: References: Comments: In-reply-to Alexander Lakhin message dated "Sun, 21 Jul 2019 08:28:53 +0300" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <17730.1563726845.1@sss.pgh.pa.us> Date: Sun, 21 Jul 2019 12:34:05 -0400 Message-ID: <17731.1563726845@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Alexander Lakhin writes: > Also, I found e-mail headers in optimizer/plan/README not relevant, so I > propose to remove them. FWIW, I think they're highly relevant, because they put a date on that text. I've not gone through that README lately, but I wouldn't be surprised if it's largely obsolete --- it hasn't been maintained in any meaningful way since Vadim wrote it. Without the headers, a reader would have no warning of that. What really ought to happen, likely, is for somebody to extract whatever is still useful there into a new(?) section in the parent directory's README. regards, tom lane