Re: [GENERAL] dblink - custom datatypes don't work
| От | Joe Conway |
|---|---|
| Тема | Re: [GENERAL] dblink - custom datatypes don't work |
| Дата | |
| Msg-id | 402A5BD6.4020203@joeconway.com обсуждение исходный текст |
| Ответ на | Re: [GENERAL] dblink - custom datatypes don't work (Joe Conway <mail@joeconway.com>) |
| Ответы |
Re: [GENERAL] dblink - custom datatypes don't work
|
| Список | pgsql-hackers |
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
В списке pgsql-hackers по дате отправления: