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 1pJ2U8-0004LT-Sa for pgsql-hackers@arkaria.postgresql.org; Sat, 21 Jan 2023 01:15:56 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pJ2U7-0002m8-NU for pgsql-hackers@arkaria.postgresql.org; Sat, 21 Jan 2023 01:15:55 +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 1pJ2R1-0005bN-Lt for pgsql-hackers@lists.postgresql.org; Sat, 21 Jan 2023 01:12:43 +0000 Received: from mail-pg1-x52e.google.com ([2607:f8b0:4864:20::52e]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1pJ2Qz-0002fC-2X for pgsql-hackers@lists.postgresql.org; Sat, 21 Jan 2023 01:12:43 +0000 Received: by mail-pg1-x52e.google.com with SMTP id 78so5395090pgb.8 for ; Fri, 20 Jan 2023 17:12:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=i4wY5Lm2A8gZQNRdff3rYX+Q5NjE+Yz+bxQJ9lEG4qo=; b=V8/hzQ14RyaeAQI8TyoRT7FkrOYIsis+VqOwGyKQujouAI1QFr6px5fZj9cOu1x33O g4HgXmQPm683ReSmJRgumzo9hzt9RxqVainYOVwzIKGNgClHwgLBFAipuFPtwCfOwowp dVNCFBwh9TlUHkmboT3IKkedQHkgXRhV0jX1xhWbA2Tm53ppGiQCQgbWQMukPnbaXAeD fVbDxhU8+O4HMT5t0OHCXQV98FT3SeZnbOvF9Vh6snO10OwnAo3WHLRebhcKaQZYLxJF VIsF3oSddSDmF9IsBVrbkPAaLaF0nV3/cjm4dF5WgF6FreiyAkDOlBOHGEbZkVbrZdwL hrpg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=i4wY5Lm2A8gZQNRdff3rYX+Q5NjE+Yz+bxQJ9lEG4qo=; b=sJgTUI2vBT0b4XR+3qg9kvGYa+BhMLpxFsPC0F5MaOfQyk2X27jZ+nZ3Ntoq/zGLgI gmfnMwX5SHDQKty6kkwsAoSxQkJvVoFKuIt2G6snmw+gCqLz1/XmvbsbWlEIzv2I8xK+ 9XP9Cyv67CddkJOQOA/4NGbYb7dnVbvGSM6T6XUfWxzPqEvZM1xhUyL4HnlVPaKeRavp W9PWwk6W5q4i8wX3ZztCFjMK1QpCHSeqe363PHRdrpyGdqDw4yO3wlekcWhW7CH4r9d9 uRfEqau3VqLsRaMesDKolmKx+reYQ4Mg/jfwGTREn8PDfOutz/0BOnoRk6Dl4XE1KqVY Ewxw== X-Gm-Message-State: AFqh2koerCs3ctmwWc75U/ik132kTfpbriHIRG1dZDdPiBbu0Ibc+Vho PPQC3Qbv6ulERJHuUCV5kCBwjdMUCTs= X-Google-Smtp-Source: AMrXdXtYrKx7qiiqYH1hH5+5yyIbd4APmjvYzGIlVpeeSP7tHhoCGcEZ4taPyW5nktusQJWxSVufoA== X-Received: by 2002:a05:6a00:2146:b0:57a:9b14:69b7 with SMTP id o6-20020a056a00214600b0057a9b1469b7mr15204938pfk.0.1674263558683; Fri, 20 Jan 2023 17:12:38 -0800 (PST) Received: from nathanxps13 ([50.47.162.83]) by smtp.gmail.com with ESMTPSA id 128-20020a621786000000b0058dbd7a5e0esm9031529pfx.89.2023.01.20.17.12.37 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 20 Jan 2023 17:12:37 -0800 (PST) Date: Fri, 20 Jan 2023 17:12:35 -0800 From: Nathan Bossart To: Alexander Pyhalov Cc: pgsql-hackers@lists.postgresql.org Subject: Re: Inconsistency in vacuum behavior Message-ID: <20230121011235.GA10739@nathanxps13> References: <21b7e2834ed78f527336cddde54846d4@postgrespro.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <21b7e2834ed78f527336cddde54846d4@postgrespro.ru> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Mon, Jan 16, 2023 at 11:18:08AM +0300, Alexander Pyhalov wrote: > Is it intended? Why don't we perform vacuum_is_permitted_for_relation() > check for inheritors in expand_vacuum_rel()? Since no lock is held on the partition, the calls to functions like object_ownercheck() and pg_class_aclcheck() in vacuum_is_permitted_for_relation() will produce cache lookup ERRORs if the relation is concurrently dropped. -- Nathan Bossart Amazon Web Services: https://aws.amazon.com