Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.4) with ESMTP id g0KLhtV41813 for ; Sun, 20 Jan 2002 16:43:55 -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 g0KLhj305614; Sun, 20 Jan 2002 16:43:45 -0500 (EST) To: Peter Eisentraut cc: 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: References: Comments: In-reply-to Peter Eisentraut message dated "Sun, 20 Jan 2002 16:11:01 -0500" Date: Sun, 20 Jan 2002 16:43:45 -0500 Message-ID: <5611.1011563025@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200201/814 X-Sequence-Number: 17817 Peter Eisentraut writes: > 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. > RTLD_LAZY allows you to load shared library modules that contain circular > references. Does that not work with RTLD_NOW? I should think it would. In any case, I'm doubtful that we care. > 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. A database restart is always very bad news in my mind. You might be right that it's too risky to make such a change now for 7.2, but I still absolutely want to do it for 7.3. regards, tom lane