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 1lbXld-0000WP-JK for pgsql-bugs@arkaria.postgresql.org; Wed, 28 Apr 2021 00:09:25 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lbXlb-0004IY-TI for pgsql-bugs@arkaria.postgresql.org; Wed, 28 Apr 2021 00:09:23 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lbXlb-0004Hp-MK for pgsql-bugs@lists.postgresql.org; Wed, 28 Apr 2021 00:09:23 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lbXlZ-0006MN-K4 for pgsql-bugs@lists.postgresql.org; Wed, 28 Apr 2021 00:09:23 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 13S095Xk2753265; Tue, 27 Apr 2021 20:09:05 -0400 From: Tom Lane To: Alvaro Herrera cc: Gavin Flower , Bruce Momjian , Noah Misch , neverov.max@gmail.com, pgsql-bugs@lists.postgresql.org Subject: Re: BUG #16939: Plural interval for negative singular In-reply-to: <20210427234438.GA22943@alvherre.pgsql> References: <20210427234438.GA22943@alvherre.pgsql> Comments: In-reply-to Alvaro Herrera message dated "Tue, 27 Apr 2021 19:44:38 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2753263.1619568545.1@sss.pgh.pa.us> Date: Tue, 27 Apr 2021 20:09:05 -0400 Message-ID: <2753264.1619568545@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Alvaro Herrera writes: > Nope -- grepping for PQprint or PQdisplayTup doesn't yield anything in > the libreoffice git repo. Hm. We actually document PQprint. While the other two entry points in that file aren't documented, they are listed in exports.txt, which means somebody *could* be calling them. I think we'd at least have to go through a long deprecation period before we could consider removing them. There are also questions of whether we can remove entry points without drawing the wrath of ABI checkers. I suppose we could dodge that by reducing them to code that returns an error. regards, tom lane