Re: some problem explicit_bzero with building PostgreSQL on linux - Mailing list pgsql-hackers

From Dimitry Markman
Subject Re: some problem explicit_bzero with building PostgreSQL on linux
Date
Msg-id MN2PR05MB63975EE919A525ECA310D39AC4B79@MN2PR05MB6397.namprd05.prod.outlook.com
Whole thread Raw
In response to Re: some problem explicit_bzero with building PostgreSQL on linux  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers

Hi Tom, thanks a lot

Adding explicit_bzero.o did the job

Thanks a lot

 

dm

 

 

From: Tom Lane <tgl@sss.pgh.pa.us>
Date: Tuesday, March 7, 2023 at 9:14 AM
To: Dimitry Markman <dmarkman@mathworks.com>
Cc: pgsql-hackers@lists.postgresql.org <pgsql-hackers@lists.postgresql.org>, Bhavya Dabas <bdabas@mathworks.com>
Subject: Re: some problem explicit_bzero with building PostgreSQL on linux

Dimitry Markman <dmarkman@mathworks.com> writes:
> how we can guaranty that if HAVE_EXPLICIT_BZERO is not defined then
> explicit_bzero function implemented in port/explicit_bzero.c will be used (just like in Darwin or windows)

Did you remember to add explicit_bzero.o to LIBOBJS in
the configured Makefile.global?

If it still doesn't work, then evidently your toolchain is selecting
the system's built-in definition of explicit_bzero over the one in
src/port/.  This is not terribly surprising given that there has to be
some amount of compiler magic involved in that function.  You may have
to resort to actually building Postgres on a platform without
explicit_bzero.

                        regards, tom lane

pgsql-hackers by date:

Previous
From: "Drouvot, Bertrand"
Date:
Subject: Re: Track IO times in pg_stat_io
Next
From: Pavel Borisov
Date:
Subject: Re: POC: Lock updated tuples in tuple_update() and tuple_delete()