Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1asBN0-0004YO-Qr for pgsql-hackers@arkaria.postgresql.org; Mon, 18 Apr 2016 15:45:50 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1asBN0-0005Vz-8c for pgsql-hackers@arkaria.postgresql.org; Mon, 18 Apr 2016 15:45:50 +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 ) id 1asBMy-0005VF-Vs for pgsql-hackers@postgresql.org; Mon, 18 Apr 2016 15:45:49 +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 ) id 1asBMr-00089w-7b for pgsql-hackers@postgresql.org; Mon, 18 Apr 2016 15:45:48 +0000 Received: from localhost (localhost [127.0.0.1]) by mail.postgrespro.ru (Postfix) with ESMTP id 7897721C7D6C; Mon, 18 Apr 2016 18:45:40 +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 86go18subpoi; Mon, 18 Apr 2016 18:45:38 +0300 (MSK) Received: from fujitsu (unknown [192.168.27.1]) by mail.postgrespro.ru (Postfix) with ESMTPSA id CD7D621C7C19; Mon, 18 Apr 2016 18:45:38 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=postgrespro.ru; s=mail; t=1460994338; bh=s3Kv2TGpHVPhe2PBx8kiXcp9D7O3drXxM+f/7/+LEkQ=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=eX3MrNc0dMu2CW1TQ7NsgknwCsSwEkRmuFwkVbT8ui3tzWB+GLHfpjyy4sn18dogn G3ai8p0ivgU8IgxdUh7MlRTRUT3P8lzerjo6VOS3FO2jzJmjw37Ro3/o7k0P5Kn0cP ZYDG1Ix9wwM0w5MOMn7jZPp+uqRT2vLRq7YU3LXk= Date: Mon, 18 Apr 2016 18:44:58 +0300 From: Aleksander Alekseev To: Pavel Stehule Cc: Tom Lane , Arcadiy Ivanov , PostgreSQL Hackers Subject: Re: Parser extensions (maybe for 10?) Message-ID: <20160418184458.51f203ab@fujitsu> In-Reply-To: References: <570C7B5A.9070309@gmail.com> <5688.1460437831@sss.pgh.pa.us> <20160418182523.3f70ad88@fujitsu> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -3.0 (---) 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 > It depends - can be allowed only one - like plpgsql extensions, or > can be serialized like pg log extensions OK, I understand "can be allowed only one". I doubt it would be a very useful feature though. I'm not sure what do you mean by "serialized like pg log extensions". Lets say extension A allows "SELECT ASAP ..." queries and extension B --- "... ORDER BY RANK". What happens when user executes "SELECT ASAP ... ORDER BY RANK" query? -- 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