Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dLmx1-0002iM-45 for pgsql-bugs@arkaria.postgresql.org; Fri, 16 Jun 2017 08:49:55 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dLmx0-0002AJ-NJ for pgsql-bugs@arkaria.postgresql.org; Fri, 16 Jun 2017 08:49:54 +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 1dLmx0-00029v-5c for pgsql-bugs@postgresql.org; Fri, 16 Jun 2017 08:49:54 +0000 Received: from mail-lf0-x242.google.com ([2a00:1450:4010:c07::242]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1dLmwy-000687-Jx for pgsql-bugs@postgresql.org; Fri, 16 Jun 2017 08:49:53 +0000 Received: by mail-lf0-x242.google.com with SMTP id x81so3374080lfb.3 for ; Fri, 16 Jun 2017 01:49:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=dhfyL/DJAnFe4y8Y2pH4X6wCiz/SGmhpGYy3kLkRMZ8=; b=qEs1bDkn1COPDNIYpfUZ8xFCu4iZ7Oz0sHJQJzAodPlsMbWQ1OFUKPZXVESQe0hxNq 9f78OlSX9HKoB+ZxvxwsVHGK7ewXnlRzC52nFZnAFAErtKmCqmHv0gV63Ld+sq1R5IhD Srbswl57kq7u/bdSGNyuFQG/HSovG1Hb2QMuZNaVqM7wgimH2hWycLXkcTepEbcjtLOO g/E92os+28i9syStAor1QxULB7TsWU0isTxIn+35deSRzKb9g+qU28j/AhenDpEZYYn+ yhu84GxvKdyP/LB7Bw2eS2ZNTTAh5euAjLpWtiMYakzDWgIL024UgTp/sdFKE9vDXI3E iAWg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:subject:to:references:cc:from:message-id :date:user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=dhfyL/DJAnFe4y8Y2pH4X6wCiz/SGmhpGYy3kLkRMZ8=; b=E5v0erPRUfLq/Znz3OtCce1VeNZR1S4Nj7KscjcCiFG2tuUd7cWbl/IqFigjeTLXvV U9G7PdfePrVVNu0Ih5rOS1ECPaJWXCzY0cd4Gd12+SW1SpG8P/zDuzYQp5gT8QjMZ/Eb tNDE/aIV3BTe4aVpRm8AMD7473rp2RTdWYY9+WWeEuDReqf8daiOOk2ThclraidUlWF9 Po7Gi4xMHsUtOQScFHaqoOU92yiZoirglrPzXepFdSZbQxOh58uc2aAlsqaz9o5a595B 4XCHPe/IIZ2ZFoBH1NDpHhru69/reyR1Wqtv+bAuEOLbodT5SXSLIyxCtyJ7ke280yuo XDNg== X-Gm-Message-State: AKS2vOzRuTF468zgSgo0cCxmAKXiSGz1RmoVC0qW23VD/fFHEgHU1Tsq flsPiDnxSE8JBg5E X-Received: by 10.25.79.25 with SMTP id d25mr3140039lfb.133.1497602990962; Fri, 16 Jun 2017 01:49:50 -0700 (PDT) Received: from [192.168.1.99] (dsl-hkibng32-54fb4e-103.dhcp.inet.fi. [84.251.78.103]) by smtp.gmail.com with ESMTPSA id o62sm429991lff.59.2017.06.16.01.49.49 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 16 Jun 2017 01:49:50 -0700 (PDT) Subject: Re: BUG #14706: Dependencies not recorded properly for base types To: Michael Paquier References: <20170614232259.1424.82774@wrigleys.postgresql.org> <22824.1497487336@sss.pgh.pa.us> <1724.1497502434@sss.pgh.pa.us> <91122adb-3afc-a727-c4c9-478175729f56@iki.fi> <11135.1497544300@sss.pgh.pa.us> <1c07c9a6-b56f-fe67-63a5-6913e78df1f6@iki.fi> Cc: Tom Lane , khuddleston@pivotal.io, PostgreSQL mailing lists From: Heikki Linnakangas Message-ID: <15dde5d7-46db-ff9b-64e1-e240535e9534@iki.fi> Date: Fri, 16 Jun 2017 11:49:48 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-bugs Precedence: bulk Sender: pgsql-bugs-owner@postgresql.org On 06/16/2017 04:54 AM, Michael Paquier wrote: > On Fri, Jun 16, 2017 at 1:38 AM, Heikki Linnakangas wrote: >> On 06/15/2017 07:31 PM, Tom Lane wrote: >>> >>> Heikki Linnakangas writes: >>>> >>>> Hmm. Strictly speaking there's no need to update the dependency when >>>> changing opaque into cstring. Because cstring is a pinned type, >>>> recordDependency will do nothing for it. >>> >>>> But in any case, I think it'd be better and simpler to fix the >>>> dependency in SetFunctionArgType() and SetFunctionReturnType() functions >>>> themselves. They're the ones that change the type, they ought to be >>>> responsible for fixing the dependency too. See attached. >>> >>> Yeah, Heikki's version looks good to me. >>> >>> Heikki, are you going to commit/backpatch this, or do you want me to? >> >> I can do it, thanks. > > Fine for me. My first quick guess was better than what I coded at the > end, the idea being to wait after TypeCreate() to get the ObjectAdress > of the new type. Ok, committed and backported, thanks! - Heikki -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs