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 1jFZ6Y-0005jY-2M for pgsql-hackers@arkaria.postgresql.org; Sat, 21 Mar 2020 08:03:38 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1jFZ6V-0007hY-L0 for pgsql-hackers@arkaria.postgresql.org; Sat, 21 Mar 2020 08:03:35 +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 1jFZ6V-0007hQ-8b for pgsql-hackers@lists.postgresql.org; Sat, 21 Mar 2020 08:03:35 +0000 Received: from mail-qt1-x831.google.com ([2607:f8b0:4864:20::831]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1jFZ6J-00049a-M6 for pgsql-hackers@postgresql.org; Sat, 21 Mar 2020 08:03:32 +0000 Received: by mail-qt1-x831.google.com with SMTP id f20so7213361qtq.6 for ; Sat, 21 Mar 2020 01:03:23 -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=RxRgseTWsTJcVUSu2VxRgUTBSnAaRe3xuKGPC6Y8bO8=; b=SGOXIHsCzpG8Sy4FXw08wEmh4qg3G3AJkFrWLQbRMcYaADrnggsL4Ptsqei9az/5U2 ojvmQgq0vF+NwlqrPnEv7J6k2B/hjfIDaInY8LtqFy0AvzoU1XtCeoL4xlfbbQgK/C4k dG4gsI5FHb45ae/6RDO+k2PsrfQvqWE1w+jDO+V1Le2/AOTE6djpPp1buJW2j7ihzYxx 2BWgd/ybYbPTIIau160qcPUffCSSNUC5KuNSYIUdGlinRKI1HgGZgYKrKkozCWLlTlBt smhTP/I0Q3KXQJwUF7NyzMEGjR2u6uNpRvAzcS9BfjNd99JL3KaSMUiSEs53TY+dKGaM VVYQ== 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=RxRgseTWsTJcVUSu2VxRgUTBSnAaRe3xuKGPC6Y8bO8=; b=Ejb233CEZktUwciJLHVSSstdmw/QYAfqdF+Wz53ZaNwiKRYUfm2Or06L8Ekh9XO71w Tyy2s+nAOlvMBZySg45Mm1c6QdiyiiW2kEV2c0ymffgrhJ/Ke126Y8L1AMv6Gj/Lrig6 reehHZL3mk+Xb//4oEupPQ624qbMsuCeyYvwF3krcftFjpC6hZnkCAtspdbT69RTVjzd ZVeR6lPVgmLIytFZK1SrnfMIhCEmeOyZPhh/cIXK6luL4qpwGwvvagzTwmmNZNKwmoR4 iOIzt5sUXQoDmKNAbXhAZWpnM1B6A2U3Hv8crYwYNqcq5ejlGNzizYI2hxuq+gdLExWI dr5g== X-Gm-Message-State: ANhLgQ3RlPIgmJyacPLNd1QIZRPrhe7Htd0qcMWsNSJB7y5b32QGngNj 5/eLHgDi9qnBzWr6JCJAm+fk3w== X-Google-Smtp-Source: ADFU+vvDmUFLqezVC/HJGEn9DHqGfCWnctawP3Cgu803gJDw7YGnjKJuwNuO1VXIX9reQ4safCILYQ== X-Received: by 2002:ac8:7b54:: with SMTP id m20mr11762807qtu.92.1584777802322; Sat, 21 Mar 2020 01:03:22 -0700 (PDT) Received: from pryzbyj (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id v187sm6171023qkc.29.2020.03.21.01.03.20 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 21 Mar 2020 01:03:21 -0700 (PDT) Received: by pryzbyj (Postfix, from userid 1000) id 71BE0800CF1; Sat, 21 Mar 2020 03:03:19 -0500 (CDT) Date: Sat, 21 Mar 2020 03:03:19 -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: <20200321080319.GF13662@telsasoft.com> References: <20200319040758.GP26184@telsasoft.com> <20200319202931.GT26184@telsasoft.com> <20200320002909.GU26184@telsasoft.com> <20200320065120.GW26184@telsasoft.com> <20200320145359.GY26184@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 Sat, Mar 21, 2020 at 01:00:03PM +0530, Amit Kapila wrote: > I have addressed your comments in the attached patch. Today, while > testing error messages from various phases, I noticed that the patch > fails to display error context if the error occurs during the truncate > phase. The reason was that we had popped the error stack in > lazy_scan_heap due to which it never calls the callback. I think we > need to set up callback at a higher level as is done in the attached > patch. I have done the testing by inducing errors in various phases > and it prints the required information. Let me know what you think of > the attached? Thanks. My tests with TRUNCATE were probably back when we had multiple push/pop cycles of local error callbacks. This passes my tests. -- Justin