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 1m9VcV-0004Kf-7Y for pgsql-hackers@arkaria.postgresql.org; Fri, 30 Jul 2021 16:44:23 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1m9VcU-0003e9-87 for pgsql-hackers@arkaria.postgresql.org; Fri, 30 Jul 2021 16:44:22 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1m9VcU-0003e1-0K for pgsql-hackers@lists.postgresql.org; Fri, 30 Jul 2021 16:44:22 +0000 Received: from mail-qk1-x729.google.com ([2607:f8b0:4864:20::729]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1m9VcS-0005pO-3a for pgsql-hackers@lists.postgresql.org; Fri, 30 Jul 2021 16:44:21 +0000 Received: by mail-qk1-x729.google.com with SMTP id f22so9999787qke.10 for ; Fri, 30 Jul 2021 09:44:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wi3ck-info.20150623.gappssmtp.com; s=20150623; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=ptltRF0Os5q4hA86Cq3N7IEH8SjeqPX/krgDWfVy9sU=; b=lZv05G87mzIajjjMpwIOvG1D2EwRYUIu2U3LMlULa4YthPGQxM0XysMkhCWaGcRny+ /uWPK7W9aR3j+3EsKHCz6TowN2H2SR2/yLUllfxNOQy6tAz0WGSjDqSfVCxdTTxrok2e 8rBZgAB2VXupB4s2V8GxYqadAimkaGdckZBTesDBpJWV64cphiaQtRDEW3GsRs7FgQqR j3T5dIqeKzSgMFDBdV7XtTT5V2FFL0O14b0POKRC6HY5dsZaeoCDPWj4PrFbDChNI73i IqemT7c1Qv5EEMnf4KjCx8OXLRBZFnT66hI10UTIjv5AW6cl7cKctvXHda4mDEsGvCYi G/7g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=ptltRF0Os5q4hA86Cq3N7IEH8SjeqPX/krgDWfVy9sU=; b=gu7aHbEJ06Vz+E/nrEvjLVaVSRGdWAYk+ee2M1NAENX5QAKfZTTBPGX0/YRiqytCX2 nfCIrQJW11CmThPgLuwMCRHcj4vm9C2+oypJKzf97p2yB5XD3/bXZNO0eRHPY1o/xHWl 2nVT1xDEj8Oc20eToui6Hm4VTYWv3kJNMRPmL2CdpiGOB2gOfnCKch8ydH+dssrDPLpU POB3M6avgVz3/nW4B7SzehYMzfSDznDZSJzsfdsKtOxD45PrkRCxEgcWl+RDMpLS0rQI h9ecrAVe/aU2lFUmTrI4amUkwI8vGPtiqDnhCoRp0IlgHYwqorMYtW37GI94f6H65cg2 vtkQ== X-Gm-Message-State: AOAM533LD3RNrJvI6liRFRZPQ7vYs2twLkuZo/IjcBXa1Kg9AnFnE7b0 As3lmrbCcS9cUbKIrdu94aYBKuBOSwwA7NTh X-Google-Smtp-Source: ABdhPJw8fNw/Re9I7SF9bLzvNkwddCE2ATa8xjp0Wiss6oJ51RcqgIgzAkqO4SHzpsws6XgGSf/mmA== X-Received: by 2002:a37:ac9:: with SMTP id 192mr3268612qkk.428.1627663458960; Fri, 30 Jul 2021 09:44:18 -0700 (PDT) Received: from jupiter.onmars.wi3ck.info (pool-71-162-210-238.phlapa.fios.verizon.net. [71.162.210.238]) by smtp.gmail.com with ESMTPSA id z6sm1146731qke.24.2021.07.30.09.44.17 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 30 Jul 2021 09:44:18 -0700 (PDT) Subject: Re: pg_upgrade does not upgrade pg_stat_statements properly To: Julien Rouhaud , Dave Cramer Cc: Bruce Momjian , PostgreSQL Hackers References: <20210730020257.jpvunvworyqsaz43@nol> <20210730103945.nc2zl74v5czy2qwd@nol> <20210730110728.tqt3oeohyvtuqqk7@nol> <20210730112832.wt3zdv32gllohope@nol> <20210730114052.smbpww3l5yw6pypi@nol> From: Jan Wieck Message-ID: <4fbc3375-db33-694b-1635-0a6796da6023@wi3ck.info> Date: Fri, 30 Jul 2021 12:44:17 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0 MIME-Version: 1.0 In-Reply-To: <20210730114052.smbpww3l5yw6pypi@nol> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 7/30/21 7:40 AM, Julien Rouhaud wrote: > On Fri, Jul 30, 2021 at 07:33:55AM -0400, Dave Cramer wrote: >> >> Ah, ok, got it, thanks. Well I'm not sure how to deal with this. >> The only thing I can think of is that we add a post_upgrade function to the >> API. >> >> All extensions would have to implement this. > > It seems like a really big hammer for a niche usage. As far as I know I'm the > only one who wrote an extension that can create different objects depending on > the server version, so I'm entirely fine with dealing with that problem in my > extension rather than forcing everyone to implement an otherwise useless API. > > Now if that API can be useful for other cases or if there are other extensions > with similar problems that would be different story. > I haven't worked on it for a while, but I think pl_profiler does the same thing, so you are not alone. Jan -- Jan Wieck