Re: elog/ereport VS misleading backtrace_function function address

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Jakub Wartak <jakub(dot)wartak(at)enterprisedb(dot)com>
Cc: Peter Eisentraut <peter(at)eisentraut(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: elog/ereport VS misleading backtrace_function function address
Date: 2024-05-14 11:41:06
Message-ID: 202405141141.ho2dj7xghmwx@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2024-May-14, Jakub Wartak wrote:

> On Sun, May 12, 2024 at 10:33 PM Peter Eisentraut <peter(at)eisentraut(dot)org> wrote:

> > Don't production builds use debug
> > symbols nowadays as well?
>
> Reality is apparently mixed,at least from what I have checked :
> - all RHEL 7.x/8.x (PGDG and our forks) do NOT come with
> --enable-debug according to pg_config.

Ooh, yeah, that's true according to
https://git.postgresql.org/gitweb/?p=pgrpms.git;a=blob;f=rpm/redhat/main/non-common/postgresql-16/main/postgresql-16.spec;h=ab2f6edc903f083e04b8f7a1d3bad8e1b7018791;hb=1a8b9fa7019d3f73322ca873b62dc0b33e73ed1d

507 %if %beta
508 --enable-debug \
509 --enable-cassert \
510 %endif

Maybe a better approach for this whole thing is to change the specs so
that --enable-debug is always given, not just for %beta.

--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexander Lakhin 2024-05-14 12:00:00 Re: Avoid orphaned objects dependencies, take 3
Previous Message Jelte Fennema-Nio 2024-05-14 11:31:13 Re: JIT compilation per plan node