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.89) (envelope-from ) id 1hUCDx-0003KD-TY for pgsql-hackers@arkaria.postgresql.org; Fri, 24 May 2019 15:35:14 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hUCDv-0004PS-RB for pgsql-hackers@arkaria.postgresql.org; Fri, 24 May 2019 15:35:11 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hUCDv-0004PL-FT for pgsql-hackers@lists.postgresql.org; Fri, 24 May 2019 15:35:11 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hUCDs-0000tA-BB for pgsql-hackers@postgresql.org; Fri, 24 May 2019 15:35:09 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id x4OFYwYe016536; Fri, 24 May 2019 11:34:58 -0400 From: Tom Lane To: Peter Eisentraut cc: Alvaro Herrera , Robert Haas , David Rowley , Amit Langote , Amit Langote , Jesper Pedersen , Rajkumar Raghuwanshi , Beena Emerson , amul sul , "pgsql-hackers@postgresql.org" , Dilip Kumar Subject: Re: [HACKERS] Runtime Partition Pruning In-reply-to: <16007.1558711252@sss.pgh.pa.us> References: <20180410213203.nl645o5vj5ap66sl@alvherre.pgsql> <16007.1558711252@sss.pgh.pa.us> Comments: In-reply-to Tom Lane message dated "Fri, 24 May 2019 11:20:52 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <16534.1558712098.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Fri, 24 May 2019 11:34:58 -0400 Message-ID: <16535.1558712098@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk I wrote: > Peter Eisentraut writes: >> What do people think about adding something like this errbacktrace() >> from =C3=81lvaro's patch to core PostgreSQL? > I think we did discuss it right after that, or somewhere nearby, and > concluded that the output is so imprecise that it's not really going > to be worth whatever portability issues we'd have to deal with. Hmm, after some digging in the archives, the closest thing I can find is this thread: https://www.postgresql.org/message-id/flat/CAMsr%2BYGL%2ByfWE%3DJvbUbnpWtr= RZNey7hJ07%2BzT4bYJdVp4Szdrg%40mail.gmail.com where we discussed using libunwind instead, but people didn't like the extra dependency. However, I stand by the assertion that glibc's backtrace() is too imprecise to be useful; I've experimented with it and despaired of being able to tell where control had actually been. regards, tom lane