Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dBsbV-0005fj-Fz for pgsql-hackers@arkaria.postgresql.org; Sat, 20 May 2017 00:50:45 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dBsbU-0002Tu-AC for pgsql-hackers@arkaria.postgresql.org; Sat, 20 May 2017 00:50:44 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dBsZx-0008Am-Op for pgsql-hackers@postgresql.org; Sat, 20 May 2017 00:49:09 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dBsZv-0003Qn-Aw for pgsql-hackers@postgresql.org; Sat, 20 May 2017 00:49:08 +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 v4K0n0Z0022756; Fri, 19 May 2017 20:49:00 -0400 From: Tom Lane To: Michael Paquier cc: "Higuchi, Daisuke" , "pgsql-hackers@postgresql.org" Subject: Re: [Bug fix]If recovery.conf has target_session_attrs=read-write, the standby fails to start. In-reply-to: References: <1803D792815FC24D871C00D17AE95905B1A34A@g01jpexmbkw24> <1803D792815FC24D871C00D17AE95905B1A4CA@g01jpexmbkw24> <24403.1495225931@sss.pgh.pa.us> Comments: In-reply-to Michael Paquier message dated "Sat, 20 May 2017 09:27:54 +0900" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <22754.1495241340.1@sss.pgh.pa.us> Date: Fri, 19 May 2017 20:49:00 -0400 Message-ID: <22755.1495241340@sss.pgh.pa.us> X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org Michael Paquier writes: > Do you think that it would be better to list the letter list for each > keyword in repl_scanner.l or have something more generic? As not that > many commands are added in the replication protocol, I would think > that this is more than enough for each command, say: > [Ss][Ll][Oo][Tt] { return K_SLOT; } > etc. Yeah, that's probably good enough. It might be worth the trouble to make out-of-line definitions, as in cubescan.l's handling of NaN and Infinity for instance, but that's just cosmetic. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers