Restore support for USE_ASSERT_CHECKING in extensions only

From: Andrew Kane <andrew(at)ankane(dot)org>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Restore support for USE_ASSERT_CHECKING in extensions only
Date: 2025-01-10 22:26:50
Message-ID: CAOdR5yHfMEMW00XGo=v1zCVUS6Huq2UehXdvKnwtXPTcZwXhmg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Prior to 6f3820f, extensions could be compiled with -DUSE_ASSERT_CHECKING
whether or not the Postgres installation was configured with
--enable-cassert (to enable at least some assertion checking). However,
after 6f3820f, linking fails with `undefined symbol:
verify_compact_attribute`. I'm not sure if this use case is officially
supported, but it has been helpful for developing pgvector.

The attached patch fixes it, but there may be a better way to do this.

Attachment Content-Type Size
v1-0001-Restore-support-for-USE_ASSERT_CHECKING-in-extens.patch application/octet-stream 1.5 KB

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2025-01-10 22:45:22 Re: Memory leak in plpython3u (with testcase and patch)
Previous Message Sami Imseih 2025-01-10 22:26:05 Re: POC: track vacuum/analyze cumulative time per relation