Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from ) id 1jGazL-0000xE-Fh for pgsql-hackers@arkaria.postgresql.org; Tue, 24 Mar 2020 04:16:27 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1jGazK-0003SI-Av for pgsql-hackers@arkaria.postgresql.org; Tue, 24 Mar 2020 04:16:26 +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_SHA1:256) (Exim 4.89) (envelope-from ) id 1jGazJ-0003Rd-U3 for pgsql-hackers@lists.postgresql.org; Tue, 24 Mar 2020 04:16:26 +0000 Received: from mail-qk1-x730.google.com ([2607:f8b0:4864:20::730]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1jGazH-0007yp-77 for pgsql-hackers@postgresql.org; Tue, 24 Mar 2020 04:16:25 +0000 Received: by mail-qk1-x730.google.com with SMTP id u4so6175769qkj.13 for ; Mon, 23 Mar 2020 21:16:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telsasoft-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=++MLNifxD0rSMZnKudnZip+9oUflJJeG/tQfgshIewU=; b=HM2n66kl2FmJzQ/faLKWRM/WsA7yxUR2ay/7imBdNdF55C2D9Axa6dSj82k6qm2BOJ alcXCvruJ7GXRSASAVAI220BaMXwsQHT4SFftfIg4S/QyFNnHusOtFmwpVvEuX3n9ftu LEVdWugaWWB7q/OtHGidCIEcUtCREQ1i1kzao0PVG37wbU/szAqpl2B0+xTkfv9Y5mUO VWE43MZtxLBaX0HhnudQWngr9OERr0SEbciVPENzdmrKbhyWfjY7PFNMCLFp+1CfLC01 fIS7aH7Qr/kIlpRoaYKevxknNCo00m6ErLcwcoYPinCjUr8CQT0Tn4p/fs1p62hILBBE Aurg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=++MLNifxD0rSMZnKudnZip+9oUflJJeG/tQfgshIewU=; b=KMP6srW1q8h/a71mZN5M1Vnd6creRQ33I2IwaJfiyQ/jYGSNumvEJjX/Bejxwcvf3R 5g3RvO8CrqEQOpQpf6+TnDR/tEbUJTgtwUUErOnhgkTifJeNxRN2uOUzZjlmo6JahoEe H8piQbKfhQprumCdxwwrdMiY2ELndgq2bLplMc8F1GlGuu1sZeGhuOmbM1rDZPjaxusJ 7w5YvwDSOdhSKfcxHgSyilLBZZyNsV6GQFUBwd+7F5msoHTelMyHbKlY98ojeK2gvto8 6r0Y62kocggYWwcuiJZkPwn+MNrI2CG2UpqMmBuQtGKMRPpSLD54X/ZUHly9dktHVbZH yZIA== X-Gm-Message-State: ANhLgQ1tuxb4L7P5HwKLPliL7dgqMqA+ZjnrI7GejrCsvKRAPHjlnXLN 5GNsBvu3feq0qj4RCfTNiON2wA== X-Google-Smtp-Source: ADFU+vt8QtN50wqPBmdiZOuJq+sE1i/OJ1ME+nZFswW2HvZUbZcKBnGOW+vw0hWnsb7zU1IcX1khlg== X-Received: by 2002:a37:cc1:: with SMTP id 184mr24450084qkm.430.1585023379470; Mon, 23 Mar 2020 21:16:19 -0700 (PDT) Received: from pryzbyj (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id y41sm13779878qtc.72.2020.03.23.21.16.18 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 23 Mar 2020 21:16:18 -0700 (PDT) Received: by pryzbyj (Postfix, from userid 1000) id 0D3EC800CF1; Mon, 23 Mar 2020 23:16:16 -0500 (CDT) Date: Mon, 23 Mar 2020 23:16:16 -0500 From: Justin Pryzby To: Amit Kapila Cc: Masahiko Sawada , Alvaro Herrera , Andres Freund , Michael Paquier , pgsql-hackers@postgresql.org Subject: Re: error context for vacuum to include block number Message-ID: <20200324041616.GA21443@telsasoft.com> References: <20200319202931.GT26184@telsasoft.com> <20200320002909.GU26184@telsasoft.com> <20200320065120.GW26184@telsasoft.com> <20200320145359.GY26184@telsasoft.com> <20200323081639.GI2563@telsasoft.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Mon, Mar 23, 2020 at 02:25:14PM +0530, Amit Kapila wrote: > > Yea, and it would be misleading if we reported "while scanning block..of > > relation" if we actually failed while writing its FSM. > > > > My previous patches did this: > > > > + case VACUUM_ERRCB_PHASE_VACUUM_FSM: > > + errcontext("while vacuuming free space map of relation \"%s.%s\"", > > + cbarg->relnamespace, cbarg->relname); > > + break; > > > > In what kind of errors will this help? If there's an I/O error on an _fsm file, for one. -- Justin