Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtp (Exim 4.84_2)
	(envelope-from
 <pgsql-hackers-owner+M297278=pgsql-hackers-arkari@postgresql.org>)
	id 1asBG2-00047j-LC
	for pgsql-hackers@arkaria.postgresql.org; Mon, 18 Apr 2016 15:38:39 +0000
Received: from localhost ([127.0.0.1] helo=postgresql.org)
	by malur.postgresql.org with smtp (Exim 4.84_2)
	(envelope-from
 <pgsql-hackers-owner+M297278=pgsql-hackers-arkari@postgresql.org>)
	id 1asBG2-0003qf-50
	for pgsql-hackers@arkaria.postgresql.org; Mon, 18 Apr 2016 15:38:38 +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 <a.alekseev@postgrespro.ru>)
	id 1asBG1-0003qZ-Fx
	for pgsql-hackers@postgresql.org; Mon, 18 Apr 2016 15:38:37 +0000
Received: from newmail.postgrespro.ru ([93.174.131.138]
 helo=mail.postgrespro.ru)
	by magus.postgresql.org with esmtp (Exim 4.84_2)
	(envelope-from <a.alekseev@postgrespro.ru>)
	id 1asBFx-0007wH-Q3
	for pgsql-hackers@postgresql.org; Mon, 18 Apr 2016 15:38:37 +0000
Received: from localhost (localhost [127.0.0.1])
	by mail.postgrespro.ru (Postfix) with ESMTP id E488021C7D6C;
	Mon, 18 Apr 2016 18:38:32 +0300 (MSK)
Received: from mail.postgrespro.ru ([127.0.0.1])
	by localhost (mail.postgrespro.ru [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id RU6T09wCWJuE; Mon, 18 Apr 2016 18:38:31 +0300 (MSK)
Received: from fujitsu (unknown [192.168.27.1])
	by mail.postgrespro.ru (Postfix) with ESMTPSA id 5201121C7C19;
	Mon, 18 Apr 2016 18:38:31 +0300 (MSK)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=postgrespro.ru;
	s=mail; t=1460993911;
	bh=dHfQIZB/hPqUn8ZJE13LKAfqRqbghSNuWzYLVav8YLI=;
	h=Date:From:To:Cc:Subject:In-Reply-To:References;
	b=Aqq2sPsxdCG4ukVx0DXXFhFt6JmOqGgDo1VhnS09qxYUfGQ/8kmGzWYzrv2hYLEJ+
	 hT75QQJzLA0AO9Z9aEI9qh22WhvH3q0glamlqHVU1tckgP8PqqR8urH68xIxMOczKY
	 NdCasF4IgeC9g3VlQ3ind08L6I7Adui609MKdO8g=
Date: Mon, 18 Apr 2016 18:37:51 +0300
From: Aleksander Alekseev <a.alekseev@postgrespro.ru>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: Should we remove unused code?
Message-ID: <20160418183751.438b2f00@fujitsu>
In-Reply-To: <25311.1460992733@sss.pgh.pa.us>
References: <20160418180711.55ac82c0@fujitsu>
	<25311.1460992733@sss.pgh.pa.us>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Pg-Spam-Score: -3.0 (---)
List-Archive: <http://archives.postgresql.org/pgsql-hackers>
List-Help: <mailto:majordomo@postgresql.org?body=help>
List-ID: <pgsql-hackers.postgresql.org>
List-Owner: <mailto:pgsql-hackers-owner@postgresql.org>
List-Post: <mailto:pgsql-hackers@postgresql.org>
List-Subscribe: <mailto:majordomo@postgresql.org?body=sub%20pgsql-hackers>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
X-Mailing-List: pgsql-hackers
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

Hello, Tom.

Thanks for your reply.

> The fact that make check-world doesn't run any code that uses some
> feature isn't a great argument for removing it.  Consider third-party
> extensions, for starters.

What is current policy regarding such sort of things? Is everything
that is in .h files considered a public API and should be backward
compatible? In this case - for how long, forever or until next major
release? Or lets say there is some API that is not used neither
internally nor by any package available on PGXN. Can we break API then?

-- 
Best regards,
Aleksander Alekseev
http://eax.me/


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers