Request a Demo
Home   >   mailing lists

Re: Question for coverage report - Mailing list pgsql-hackers

From Jacob Champion
Subject Re: Question for coverage report
Date
Msg-id CAOYmi+=REXfz+=9L0MdtCatkXtRkuXr+v1w8=81M2esZNQZsHQ@mail.gmail.com
Whole thread Raw
In response to Re: Question for coverage report  (Álvaro Herrera <alvherre@kurilemu.de>)
Responses Re: Question for coverage report
List pgsql-hackers
Tree view 
On Fri, Oct 17, 2025 at 2:15 PM Álvaro Herrera <alvherre@kurilemu.de> wrote:
> Hmm, these reports are supposed to have been generated with -O0.  This
> is the configure line:
>
> ./configure --cache-file=/home/coverage/pgsrc/configure.cache --enable-depend --enable-coverage --enable-tap-tests
--enable-nls--with-python --with-perl --with-tcl --with-openssl --with-libxml --with-ldap --with-pam --with-llvm
--with-lz4--enable-injection-points CFLAGS=-O0 'CPPFLAGS=-DCOPY_PARSE_PLAN_TREES -DWRITE_READ_PARSE_PLAN_TREES
-DRAW_EXPRESSION_COVERAGE_TEST'LLVM_CONFIG=/usr/bin/llvm-config-19 CLANG=clang-19 >> $LOG 2>&1 
>
> Is this somehow not effective?

Are you able to double-check the compiler invocation for pgoutput.c?

--Jacob

pgsql-hackers by date:

Previous
From: Philip Alger
Date:
Subject: Re: [PATCH] Add pg_get_trigger_ddl() to retrieve the CREATE TRIGGER statement
Next
From: Sami Imseih
Date:
Subject: Re: Skip unregistered custom kinds on stats load