Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1e4T7F-0000vY-6q for pgsql-bugs@arkaria.postgresql.org; Tue, 17 Oct 2017 14:45:09 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1e4T7E-0005zy-Pm for pgsql-bugs@arkaria.postgresql.org; Tue, 17 Oct 2017 14:45:08 +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_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1e4T6U-0003Q0-FR for pgsql-bugs@postgresql.org; Tue, 17 Oct 2017 14:44:22 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1e4T6R-0006bz-Lw for pgsql-bugs@postgresql.org; Tue, 17 Oct 2017 14:44:22 +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 v9HEiHT4015820; Tue, 17 Oct 2017 10:44:17 -0400 From: Tom Lane To: boatcoder@gmail.com cc: pgsql-bugs@postgresql.org Subject: Re: BUG #14859: Config file parsing is allergic to spaces on last line of file In-reply-to: <20171017141814.8203.27280@wrigleys.postgresql.org> References: <20171017141814.8203.27280@wrigleys.postgresql.org> Comments: In-reply-to boatcoder@gmail.com message dated "Tue, 17 Oct 2017 14:18:14 -0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <15818.1508251457.1@sss.pgh.pa.us> Date: Tue, 17 Oct 2017 10:44:17 -0400 Message-ID: <15819.1508251457@sss.pgh.pa.us> List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-bugs Precedence: bulk Sender: pgsql-bugs-owner@postgresql.org boatcoder@gmail.com writes: > Edit your pg_hba.conf file, add a space (without a new line) at the end of > the file. > Attempt to start postgres. It will fail with messages like this. Hmph. I can reproduce this in 9.6 and earlier, but not in v10 or HEAD. Apparently somebody fixed it by accident. Looking ... regards, tom lane -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs