Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.4) with ESMTP id g0LK4ml26687 for ; Mon, 21 Jan 2002 15:04:48 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id g0LH3Of09787; Mon, 21 Jan 2002 12:03:24 -0500 (EST) To: Bruce Momjian cc: Christopher Kings-Lynne , David Terrell , Brent Verner , Murray Prior Hobbs , Lamar Owen , pgsql-hackers@postgresql.org Subject: Re: RTLD_LAZY considered harmful (Re: pltlc and pltlcu problems) In-reply-to: <200201211309.g0LD9a421146@candle.pha.pa.us> References: <200201211309.g0LD9a421146@candle.pha.pa.us> Comments: In-reply-to Bruce Momjian message dated "Mon, 21 Jan 2002 08:09:36 -0500" Date: Mon, 21 Jan 2002 12:03:24 -0500 Message-ID: <9784.1011632604@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200201/892 X-Sequence-Number: 17891 Bruce Momjian writes: > Interesting LAZY has better efficiency. "Efficiency" by what measure? I would think that batch resolution of symbols would be faster than taking a trap for each one. > 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. (a) How are they going to find out if the object files are bad, other than by crashing their database? I *really* don't like the attitude that a backend crash is okay. Under any circumstances, development or not. (b) Badness may depend on context, eg LD_LIBRARY_PATH. So it's not really safe to assume that if it worked before then you don't have to worry about it crashing you in production. regards, tom lane