From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Joe Conway <mail(at)joeconway(dot)com> |
Cc: | Mark Gibson <gibsonm(at)cromwell(dot)co(dot)uk>, "Hackers (PostgreSQL)" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [GENERAL] dblink - custom datatypes don't work |
Date: | 2004-02-11 16:53:01 |
Message-ID: | 22013.1076518381@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers pgsql-patches |
Joe Conway <mail(at)joeconway(dot)com> writes:
> I'd add that when working with shared libraries, you need to make sure
> they are loaded before you attach to the process (I think there is a way
> to deal with it after the fact, but I'm not sure of the details).
On HPUX, I find that "sharedlibrary /path/to/library" works to teach gdb
about symbols in a freshly loaded library. (Occasionally it seems to be
needed for libraries that were already present at attach time, too.)
Not sure if this applies to other OSes, but give it a try.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-02-11 16:57:41 | Re: DB cache size strategies |
Previous Message | Richard Huxton | 2004-02-11 16:50:00 | Re: pl/pythonu |
From | Date | Subject | |
---|---|---|---|
Next Message | Mike Benoit | 2004-02-11 17:32:22 | Re: Summary of Changes since last release (7.4.1) |
Previous Message | Joe Conway | 2004-02-11 16:44:06 | Re: [GENERAL] dblink - custom datatypes don't work |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2004-02-11 17:29:54 | Threading bug |
Previous Message | Joe Conway | 2004-02-11 16:44:06 | Re: [GENERAL] dblink - custom datatypes don't work |