Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1drWWR-00079T-Sa for pgsql-hackers@arkaria.postgresql.org; Mon, 11 Sep 2017 21:45:39 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1drWWR-0002MG-F8 for pgsql-hackers@arkaria.postgresql.org; Mon, 11 Sep 2017 21:45:39 +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 1drWWP-0002KG-Tw for pgsql-hackers@postgresql.org; Mon, 11 Sep 2017 21:45:37 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1drWWM-0004bI-MN for pgsql-hackers@postgresql.org; Mon, 11 Sep 2017 21:45:37 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id v8BLjSkF005909; Mon, 11 Sep 2017 17:45:28 -0400 From: Tom Lane To: Dmitry Dolgov <9erthalion6@gmail.com> cc: Arthur Zakirov , David Steele , Peter Eisentraut , PostgreSQL-development Subject: Re: [PATCH] Generic type subscripting In-reply-to: References: <3939224.Pu1MPp1GC3@zakirov> <20170909213349.GA17898@arthur.localdomain> <4675.1505164755@sss.pgh.pa.us> Comments: In-reply-to Dmitry Dolgov <9erthalion6@gmail.com> message dated "Mon, 11 Sep 2017 23:33:20 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <5906.1505166328.1@sss.pgh.pa.us> Date: Mon, 11 Sep 2017 17:45:28 -0400 Message-ID: <5907.1505166328@sss.pgh.pa.us> 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 Dmitry Dolgov <9erthalion6@gmail.com> writes: >> On 11 September 2017 at 23:19, Tom Lane wrote: >> Uh, what? Sure you can. Just because the existing code never has a >> reason to create such a dependency doesn't mean it wouldn't work. > Well, I thought that `pg_depend` was not intended to be used from > user-defined code and it's something "internal". Well, no, we're not expecting that SQL code will manually insert rows there. This feature should have some sort of SQL command that will set up the relevant catalog entries, including the dependencies. If you don't want to do that, you're going to need the runtime tests. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers