Re: RTLD_LAZY considered harmful (Re: pltlc and pltlcu

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Brent Verner <brent(at)rcfile(dot)org>, Murray Prior Hobbs <murray(at)efone(dot)com>, Lamar Owen <lamar(dot)owen(at)wgcr(dot)org>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: RTLD_LAZY considered harmful (Re: pltlc and pltlcu
Date: 2002-01-20 21:11:01
Message-ID: Pine.LNX.4.30.0201201604510.712-100000@peter.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-sql

Tom Lane writes:

> Unless I hear a credible counter-argument, I am going to change
> RTLD_LAZY to RTLD_NOW in src/backend/port/dynloader/linux.h. I have
> tested that and it produces a clean error with no backend crash.
>
> What I would *like* to do is make the same change in all the
> port/dynloader files that reference RTLD_LAZY:

RTLD_LAZY allows you to load shared library modules that contain circular
references. I don't know if that's useful or just stupid, but on some
systems the shared library models are pretty, um, different so that the
need for this might arise from time to time.

> However I'm a bit scared to do that at this late stage of the release
> cycle, because perhaps some of these platforms don't support the full
> dlopen() API. Comments? Can anyone test whether RTLD_NOW works on
> any of the above-mentioned ports?

I really don't think this is a good change to make now, as we don't know
how well all of this is supported, and the failure scenario is annoying
but not really that harmful.

--
Peter Eisentraut peter_e(at)gmx(dot)net

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2002-01-20 21:12:45 Re: pltlc and pltlcu problems
Previous Message alavoor 2002-01-20 21:03:41 PostgreSQL Licence: GNU/GPL

Browse pgsql-sql by date

  From Date Subject
Next Message Peter Eisentraut 2002-01-20 21:12:45 Re: pltlc and pltlcu problems
Previous Message Tom Lane 2002-01-20 20:58:14 Re: pltlc and pltlcu problems