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 g0LJpSl06715 for ; Mon, 21 Jan 2002 14:51:28 -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 g0LGsiZ16622; Mon, 21 Jan 2002 11:54:44 -0500 (EST) From: Bruce Momjian Message-Id: <200201211654.g0LGsiZ16622@candle.pha.pa.us> Subject: Re: RTLD_LAZY considered harmful (Re: pltlc and pltlcu problems) In-Reply-To: To: Peter Eisentraut Date: Mon, 21 Jan 2002 11:54:44 -0500 (EST) CC: Christopher Kings-Lynne , David Terrell , Tom Lane , 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/869 X-Sequence-Number: 17870 Peter Eisentraut wrote: > 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. OK, I was just throwing out the point in case it was significant. -- 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