Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1c2L9N-0006Xe-6k for pgsql-hackers@arkaria.postgresql.org; Thu, 03 Nov 2016 16:46:01 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1c2L9M-0005KM-Ps for pgsql-hackers@arkaria.postgresql.org; Thu, 03 Nov 2016 16:46:00 +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 1c2L7s-0002Ch-RE for pgsql-hackers@postgresql.org; Thu, 03 Nov 2016 16:44:28 +0000 Received: from out2-smtp.messagingengine.com ([66.111.4.26]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1c2L7l-0004dq-Tx for pgsql-hackers@postgresql.org; Thu, 03 Nov 2016 16:44:27 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 9B80920929; Thu, 3 Nov 2016 12:44:20 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute2.internal (MEProxy); Thu, 03 Nov 2016 12:44:20 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= smtpout; bh=Tt+WqTsTIpCbQxXq9BkuXWk9c20=; b=RkRORSzQRo8yxV1xpbou ibLS/dkVTaAD9Fk88WjoX86kGErBLlGKrU0yLj+8LkEt+arJ85P4DcKS2wW/8Hr/ +PE9jIVc01HePxGQPQBHu1BAVlwnhhxskPZO3rlKQsfLAb9QndOOuqGZ9KLc19/F ga3TamxoSDeNwfKZlExMkks= X-ME-Sender: X-Sasl-enc: JKv967rlUWowVGrVhZZe+WuzVNOIxm45HRpS5DgJO8D4 1478191458 Received: from april.local (c-73-13-66-39.hsd1.pa.comcast.net [73.13.66.39]) by mail.messagingengine.com (Postfix) with ESMTPA id 96601CC083; Thu, 3 Nov 2016 12:44:18 -0400 (EDT) Subject: Re: add more NLS to bin To: Michael Paquier References: Cc: pgsql-hackers From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: Date: Thu, 3 Nov 2016 12:44:18 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.6 (--) 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 On 10/31/16 1:58 AM, Michael Paquier wrote: > 2) For 0002 and pg_test_fsync, I am seeing a missing entry: > printf(NA_FORMAT, "n/a*\n"); ok > 4) 0004 and pg_upgrade... In check.c, three places like that: > if (!db_used) > { > fprintf(script, "Database: %s\n", active_db->db_name); > db_used = true; > } > > In exec.c: > #endif > fprintf(log, "command: %s\n", cmd); > #ifdef WIN32 These and several of the other places write into log or script files. I have chosen not to do anything about those for now. That might be a future change, or we just leave them. > +GETTEXT_FLAGS = \ > + pg_fatal:1:c-format \ > + pg_log:2:c-format \ > + prep_status:1:c-format \ > + report_stats:2:c-forma > s/report_stats/report_status/ ok > In info.c, missing some entries in report_unmatched_relation() when > reporting unmatching relations? Yeah, that will need a bit of a rewrite, so FIXME later? > In util.c, doesn't pg_log_v() need to handle strings used in fprintf? Which specific lines do you have in mind? -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers