Received: from candle.pha.pa.us (216-55-132-35.dsl.san-diego.abac.net [216.55.132.35]) by postgresql.org (8.11.3/8.11.4) with ESMTP id g0KJBGV09463 for ; Sun, 20 Jan 2002 14:11:16 -0500 (EST) (envelope-from pgman@candle.pha.pa.us) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.10.1) id g0KJArH15682; Sun, 20 Jan 2002 14:10:53 -0500 (EST) From: Bruce Momjian Message-Id: <200201201910.g0KJArH15682@candle.pha.pa.us> Subject: Re: RTLD_LAZY considered harmful (Re: pltlc and pltlcu problems) In-Reply-To: <4640.1011552017@sss.pgh.pa.us> To: Tom Lane Date: Sun, 20 Jan 2002 14:10:53 -0500 (EST) CC: Brent Verner , Murray Prior Hobbs , Lamar Owen , pgsql-hackers@postgresql.org X-Mailer: ELM [version 2.4ME+ PL96 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Archive-Number: 200201/809 X-Sequence-Number: 17813 > 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 can confirm that RTLD_NOW exists on BSD/OS. Can we do: #ifdef RTLD_NOW use RTLD_NOW #else whatever_is_there_now #endif in those ports at least for 7.2 so we can be sure we don't get failures. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026