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 1ny6Gc-000297-LO for pgsql-bugs@arkaria.postgresql.org; Mon, 06 Jun 2022 06:31:10 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1ny6Ga-0005M1-8i for pgsql-bugs@arkaria.postgresql.org; Mon, 06 Jun 2022 06:31:08 +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 1ny6GZ-0005Ls-P4 for pgsql-bugs@lists.postgresql.org; Mon, 06 Jun 2022 06:31:08 +0000 Received: from mail-qt1-x82b.google.com ([2607:f8b0:4864:20::82b]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1ny6GU-0003fC-Qk for pgsql-bugs@lists.postgresql.org; Mon, 06 Jun 2022 06:31:07 +0000 Received: by mail-qt1-x82b.google.com with SMTP id hf10so9746096qtb.7 for ; Sun, 05 Jun 2022 23:31:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leadboat.com; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=AQh9s1HwhNmAg+E84uoj3nT5NvXS07flJynpIn6I9XE=; b=ArZ7HW2/ZVHgIfO/+X5DnQHex5DkT4I4cxIWUCHsNu9DsrNwkA3hg7bdA/bF4BKd/U Khs+FXsOzF91VOgz/pIfBMDdmzcUfMPO0OTToHFdL+mCpPXHnnnToSnjth8dDpzmnNJw 0VmzOBbo8d17bv89Y04PohNe2MMvU8Mqf1QMo= 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:user-agent; bh=AQh9s1HwhNmAg+E84uoj3nT5NvXS07flJynpIn6I9XE=; b=XeMQaEZHthUQK1NJ7ziKyKfAxxKdVknQmK5FjI4Rwe5wt3M7ouhVoGLMzPq6qWFanJ gr8SeDIN3WrqmQGH7XJPXvD8UbDMQU8aIH0NKQKwjr9/jSc32LLGbCMc0lu1g+sE4dIg +RdA1oWqwTAB/tbG6vrR+JMUm1Gy2MDEJKcucEoR0Zuhg22h5X93c8cZ7Vlzcqg3t8zS 4IT2LAuWgP3Lwwehs8u3Jyctv6Nmwh9oOOpc9PgjD4mi96hKrZcaHxad+r7EZjiVxi69 tCRxlV7Nfa9ZOPt6GXLi7PA083n8YIotwJtalat1ggqVvjTGEGcbugNwXHvpthGSpxcF Y1NQ== X-Gm-Message-State: AOAM531wyhsEm8asS7YUoUI7U6crZEjrLsaJ2bbBpM+LfT8ev9zCDAwq XsCxTgxoh/+Tka/IgoNGE2I+9g== X-Google-Smtp-Source: ABdhPJygw15f9+RHVQja+OwWPobTXtBhp72uqG/cwiVQwRtCMZaAhO/yz/fAdPEOolTRMvAhBmeb8w== X-Received: by 2002:ac8:7f10:0:b0:304:e88d:b6c1 with SMTP id f16-20020ac87f10000000b00304e88db6c1mr5772920qtk.364.1654497060671; Sun, 05 Jun 2022 23:31:00 -0700 (PDT) Received: from rfd.leadboat.com ([2600:1702:a20:5750::2e]) by smtp.gmail.com with ESMTPSA id bz11-20020a05622a1e8b00b002f77a8bc37fsm9850673qtb.51.2022.06.05.23.30.58 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 05 Jun 2022 23:30:59 -0700 (PDT) Date: Sun, 5 Jun 2022 23:30:56 -0700 From: Noah Misch To: Nathan Bossart Cc: Michael Paquier , 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: <20220606063056.GA3527347@rfd.leadboat.com> 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> <20220603181724.GA2672350@nathanxps13> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220603181724.GA2672350@nathanxps13> User-Agent: Mutt/1.5.24 (2015-08-30) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Fri, Jun 03, 2022 at 11:17:24AM -0700, Nathan Bossart wrote: > 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. That would not surprise me. Do you have what you need to continue?