Re: elog(FATAL) vs shared memory
От
Jim Nasby
Тема
Re: elog(FATAL) vs shared memory
Дата
Msg-id
DC5995BC-9E10-46B0-8084-4607274391DC@decibel.org
Ответ на
Re: elog(FATAL) vs shared memory (Jim Nasby)
Список
Дерево обсуждения
elog(FATAL) vs shared memory Tom Lane <tgl@sss.pgh.pa.us>
Re: elog(FATAL) vs shared memory Bruce Momjian <bruce@momjian.us>
Re: elog(FATAL) vs shared memory Tom Lane <tgl@sss.pgh.pa.us>
Re: elog(FATAL) vs shared memory Bruce Momjian <bruce@momjian.us>
Re: elog(FATAL) vs shared memory Mark Shuttleworth <mark@ubuntu.com>
Re: elog(FATAL) vs shared memory Stuart Bishop <stuart.bishop@canonical.com>
Re: elog(FATAL) vs shared memory Jim Nasby <decibel@decibel.org>
Re: elog(FATAL) vs shared memory Jim Nasby <decibel@decibel.org>
Re: elog(FATAL) vs shared memory Stuart Bishop <stuart.bishop@canonical.com>
Re: elog(FATAL) vs shared memory Tom Lane <tgl@sss.pgh.pa.us>
Re: elog(FATAL) vs shared memory Mark Shuttleworth <mark@ubuntu.com>
Re: elog(FATAL) vs shared memory Stuart Bishop <stuart.bishop@canonical.com>
Re: elog(FATAL) vs shared memory Heikki Linnakangas <heikki@enterprisedb.com>
Re: elog(FATAL) vs shared memory Gregory Stark <stark@enterprisedb.com>
On Apr 11, 2007, at 6:23 PM, Jim Nasby wrote: > FWIW, you might want to put some safeguards in there so that you > don't try to inadvertently kill the backend that's running that > function... unfortunately I don't think there's a built-in function > to tell you the PID of the backend you're connected to; if you're > connecting via TCP you could use inet_client_addr() and > inet_client_port(), but that won't work if you're using the socket > to connect. *wipes egg off face* There is a pg_backend_pid() function, even if it's not documented with the other functions (it's in the stats function stuff for some reason). -- Jim Nasby jim@nasby.net EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
В списке pgsql-hackers по дате отправления
От: Merlin Moncure
Дата: