Re: [PORTS] Failed install - libgen.so doesn't exist

"Rocco Altier" <[email protected]>
Newsgroups gmane.comp.db.postgresql.ports
Message-ID <[email protected]>
Is there an easy way to tell what symbols are being used by Postgres?

For example, I was looking into libPW, and I want to see which symbols
might be used, but I don't see any being pulled into postgres binary or
the other commands.

BTW, from what I am reading is not thread-safe, so I wonder if we should
be including it even when we find it.  Or what possible calls we might
be using from it.

	-rocco


> -----Original Message-----
> From: [email protected] 
> [mailto:[email protected]] On Behalf Of Tom Lane
> Sent: Wednesday, February 01, 2006 12:11 PM
> To: Bruce Momjian
> Cc: Larry Rosenman; [email protected]; [email protected]
> Subject: Re: [PORTS] Failed install - libgen.so doesn't exist 
> 
> 
> Bruce Momjian <[email protected]> writes:
> > Larry Rosenman wrote:
> >> the issue is whether they actually export symbols that are NEEDED.
> 
> > Yea, ouch.  This is going to be a pain.
> 
> What I had in mind was to run "nm --ext --def" or local equivalent
> on each library, and then pick out a few symbols that look plausible
> to test for (or just send 'em all to the list if you are lazy).  We
> want to pick a symbol for each library that (a) is actually referenced
> by Postgres and (b) exists in that library on all our platforms that
> need that library.
> 
> 			regards, tom lane
> 
> ---------------------------(end of 
> broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
>        choose an index scan if your joining column's datatypes do not
>        match
> 

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
       choose an index scan if your joining column's datatypes do not
       match
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.