Re: [GENERAL] dblink - custom datatypes don't work

From: Joe Conway <mail(at)joeconway(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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:44:06
Message-ID: 402A5BD6.4020203@joeconway.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers pgsql-patches

Tom Lane wrote:
> It's not hard. Start psql, then in another window use ps to determine
> the PID of the connected backend. (The pg_stat_activity view might help
> too.) Then
>
> gdb /path/to/postgres-executable PID
> gdb> b whereever
> gdb> cont
>
> and away you go.

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). To do
that, either execute a function in the library (e.g. select
dblink_connect...) or use the LOAD command like this:

regression=# load '$libdir/dblink';
LOAD

HTH,

Joe

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ed L. 2004-02-11 16:47:35 Re: DB cache size strategies
Previous Message Tom Lane 2004-02-11 16:43:19 Re: Function parameters of rowtype

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2004-02-11 16:53:01 Re: [GENERAL] dblink - custom datatypes don't work
Previous Message Tom Lane 2004-02-11 16:39:16 Re: [GENERAL] dblink - custom datatypes don't work

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2004-02-11 16:53:01 Re: [GENERAL] dblink - custom datatypes don't work
Previous Message Tom Lane 2004-02-11 16:39:16 Re: [GENERAL] dblink - custom datatypes don't work