Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jfb3Y-00033R-Qc for pljava-dev@arkaria.postgresql.org; Mon, 01 Jun 2020 03:24:08 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jfb3W-0008Tq-50 for pljava-dev@arkaria.postgresql.org; Mon, 01 Jun 2020 03:24:06 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jfb3V-0008Tj-LL for pljava-dev@lists.postgresql.org; Mon, 01 Jun 2020 03:24:05 +0000 Received: from anastigmatix.net ([68.171.219.55]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jfb3P-0006vg-AF for pljava-dev@lists.postgresql.org; Mon, 01 Jun 2020 03:24:04 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=anastigmatix.net; s=default; h=Content-Transfer-Encoding:Content-Type: In-Reply-To:MIME-Version:Date:Message-ID:From:Cc:References:To:Subject:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=WIgDlnj0UUMH7YPbtot45GyIoDHzB3/jGTluJzxpzoQ=; b=YtIwiA5uJ5PUA7ISfYGYcn3tIG k7muhI0Whct1HbLqwIAF6d5SIlkIusxcXTpGoJu0nYvN5lsxbeaEkrM9OssI0sD5utor7b2emkTO4 PhYDfURnW5tPYwdkxAWDwWGKWw/c82d0kJHyYFgvUudp1pFQHjBgfZ2rYoo0zxN4vefTp37SFYwMa 3cfgUagKahPM0U9FxC/DlBrSdduOQbvd17krXmUbYrbUdFy3E8JIPTvRf+uzeUecU8CUl3H6iC7OK pnAv65qo3WseepDmbK6oBIwMxPLqlcQFgRdazC25beqnCDli+bjqSTr50N63/pnZ/QtZ/uU34uMjU xfOdSOHA==; Received: from [184.19.31.139] (port=55704) by bay.acenet.us with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.93) (envelope-from ) id 1jfb3L-000Kms-AK; Sun, 31 May 2020 23:23:55 -0400 Subject: Re: Starting build-system work (Windows/Mac users please speak up) To: Kartik Ohri References: <5EC17E17.7070002@anastigmatix.net> <5ECED046.3000308@anastigmatix.net> <5ED0FCB0.405@anastigmatix.net> <5ED10C6D.2020000@anastigmatix.net> <5ED10F36.7060304@anastigmatix.net> <5ED15825.9060504@anastigmatix.net> <5ED270BA.9010001@anastigmatix.net> <5ED3D488.1010401@anastigmatix.net> Cc: pljava-dev@lists.postgresql.org From: Chapman Flack X-Enigmail-Draft-Status: N1110 Message-ID: <5ED474CA.3000106@anastigmatix.net> Date: Sun, 31 May 2020 23:23:54 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.0 MIME-Version: 1.0 In-Reply-To: <5ED3D488.1010401@anastigmatix.net> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-OutGoing-Spam-Status: No, score=-95.0 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - bay.acenet.us X-AntiAbuse: Original Domain - lists.postgresql.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - anastigmatix.net X-Get-Message-Sender-Via: bay.acenet.us: authenticated_id: chap@anastigmatix.net X-Authenticated-Sender: bay.acenet.us: chap@anastigmatix.net X-Source: X-Source-Args: X-Source-Dir: X-From-Rewrite: unmodified, already matched List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 05/31/20 12:00, Chapman Flack wrote: >> - Messages from the JVM itself that are emitted through a 'vfprintf hook' >> are caught by PL/Java's hook [1] and injected into PostgreSQL's >> elog system at a selectable level, usually INFO. (That is probably >> the path being followed by the -Xcheck:jni messages, explaining >> why they have INFO: in front.) Exploiting that fact, I decided to just condense out those messages (only the ones coming from Java's own JMX classes, outside our power to fix) right at the source, by putting a small state machine in the vfprintf hook to recognize and not log them. That's in PR #276. Also in that PR, changes to fix the remaining -Xcheck:jni messages that were really coming from PL/Java. For the moment, in my environment, with PR #275 and #276 applied, it builds and tests -Xcheck:jni clean. That should eliminate any need for doing fancy stuff with those messages in the CI configuration. Any new issues that crop up in development later ought to produce a smaller volume of messages that we want to know about. Regards, -Chap