Re: RTLD_LAZY considered harmful (Re: pltlc and pltlcu

Peter Eisentraut <peter_e@gmx.net>

From: Peter Eisentraut <peter_e@gmx.net>

To: Bruce Momjian <pgman@candle.pha.pa.us>

Cc: Christopher Kings-Lynne <chriskl@familyhealth.com.au>, David Terrell <dbt@meat.net>, Tom Lane <tgl@sss.pgh.pa.us>, Brent Verner <brent@rcfile.org>, Murray Prior Hobbs <murray@efone.com>, Lamar Owen <lamar.owen@wgcr.org>, <pgsql-hackers@postgresql.org>

Date: 2002-01-21T16:50:26Z

Lists: pgsql-hackers

Bruce Momjian writes:

> Interesting LAZY has better efficiency.  Seems we should just keep LAZY
> as our default for future releases and tell people if they link to bad
> object files, they should expect trouble.

In practice, we load object files only if we call the function, so symbol
resolution happens either way briefly after loading.  RTLD_NOW includes
some overhead because it checks symbols that we might not end up needing,
but for the typical PostgreSQL extension module, that should really not
matter.

-- 
Peter Eisentraut   peter_e@gmx.net