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 1nxBra-0002yU-6j for pgsql-bugs@arkaria.postgresql.org; Fri, 03 Jun 2022 18:17:34 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nxBrY-0002Jr-C8 for pgsql-bugs@arkaria.postgresql.org; Fri, 03 Jun 2022 18:17:32 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nxBrY-0002Ji-1K for pgsql-bugs@lists.postgresql.org; Fri, 03 Jun 2022 18:17:32 +0000 Received: from mail-il1-x12d.google.com ([2607:f8b0:4864:20::12d]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nxBrV-0005oj-CB for pgsql-bugs@lists.postgresql.org; Fri, 03 Jun 2022 18:17:31 +0000 Received: by mail-il1-x12d.google.com with SMTP id r3so7900644ilt.8 for ; Fri, 03 Jun 2022 11:17:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=k/0NqDZY320h8Whh7aE/GEjutDtMMQ5ShL7PE6B3UWw=; b=ECb3FOnv/N/MEN4A/tANPMMb8EStJpqL7Lzq60OENHnlhkNONUaOzjCGKZr80vrBrK oxlckCpVZC1h+q8sbpiAZnz+RfKoAomM7QlCPtwn87farBPumMnUXNy1GHozKj/sbYcb /qY72YtmK9yxVUom3BA6dr7btGegAalpuzXoLDOPggm2xk1KvDMLax8irwwAejwfIcM5 3TPulaU/BU8vWDXgL/dxQcQlyWnw0UWKMrO6Qb/xpTze1xVpLdvIM+HdJleLj7oBqBt5 JZXqITyIg+MpRAtg5k3pUZSJVnHF1q1MMXNt5GU05VIHO3Txqcthh0PA84z9h9hXHUV4 ukzA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=k/0NqDZY320h8Whh7aE/GEjutDtMMQ5ShL7PE6B3UWw=; b=uee4eXCxfI4qjIT+i7AfL0cC1eY6BgV9Ij/nJJ0fYnNrHWDLgmdxF2hl2Cjhd0gLqp UY+JBgL93fEbW1pl28glWrQ9viEPswDswsBV1kPUw20GXpSffLm8imV9ZMGHP/L4Yw5L sTBiRFKL9E6bw/2Z5y4PhkNWndK1mxGmZMX/tcJaxLQGpmQkTnA1vFbnD4hGSWuoyEZN MpTM/GWmFgczGQvnFQxNmHa0Mfvkv+DMAIgMxaKdiVjBojYPX8OlcEXSzlrYbVnpwBPK KY0CeuTy/3l5dHKGic7nxgt73/XbFr6DL4Bt420mm5m52rnrL+JDdY4RzgCIb2HedwjC eoLQ== X-Gm-Message-State: AOAM533VkPOwYgW8w6+OmxwwMwWZofAwlX5AiViyS02uUW//2fNT1vRP FR69D3EKyA3lfX2hSGFEzmE= X-Google-Smtp-Source: ABdhPJy5P6kR/LSITjLvhENoTm1oQ0he44NrABhuK34lvqo5lVgtrMwR+uCqRKRGLzaRwn1x5zi8ow== X-Received: by 2002:a05:6e02:2161:b0:2d3:d5e4:1574 with SMTP id s1-20020a056e02216100b002d3d5e41574mr6506615ilv.1.1654280246997; Fri, 03 Jun 2022 11:17:26 -0700 (PDT) Received: from nathanxps13 ([2600:1700:48f8:340f:dba8:1e2e:7a96:89d0]) by smtp.gmail.com with ESMTPSA id s2-20020a5edc42000000b0066580930265sm2657165iop.14.2022.06.03.11.17.25 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 03 Jun 2022 11:17:26 -0700 (PDT) Date: Fri, 3 Jun 2022 11:17:24 -0700 From: Nathan Bossart To: Michael Paquier Cc: Noah Misch , pgsql-bugs@lists.postgresql.org, =?iso-8859-1?Q?F=E4rber=2C_Franz-Josef_=28StMUK=29?= , Tom Lane Subject: Re: Extension pg_trgm, permissions and pg_dump order Message-ID: <20220603181724.GA2672350@nathanxps13> References: <1961551.1653498155@sss.pgh.pa.us> <20220526055047.GA3153526@rfd.leadboat.com> <20220528045122.GA3228881@rfd.leadboat.com> <20220529033033.GA1973706@nathanxps13> <20220529043403.GB3265235@rfd.leadboat.com> <20220531152855.GA2236210@nathanxps13> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220531152855.GA2236210@nathanxps13> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Tue, May 31, 2022 at 08:28:55AM -0700, Nathan Bossart wrote: > I've spent some time looking at all the code impacted by a117ceb and > 0abc1a0, and I've yet to identify any additional problems besides the one > with ResolveOpClass(). However, I'm far from confident in this analysis, > and I still need to try out the ereport() approach that Noah suggested. I > would welcome any assistance identifying other problem areas. Ah, I think I am missing something. For example, the code that identifies the exclusion operator (immediately following the call to ResolveOpClass()) is likely subject to a similar problem. -- Nathan Bossart Amazon Web Services: https://aws.amazon.com