Re: elog(FATAL) vs shared memory

From: Jim Nasby <decibel(at)decibel(dot)org>
To: Jim Nasby <decibel(at)decibel(dot)org>
Cc: Stuart Bishop <stuart(dot)bishop(at)canonical(dot)com>, Mark Shuttleworth <mark(at)ubuntu(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgreSQL(dot)org, Martin Pitt <martin(dot)pitt(at)ubuntu(dot)com>
Subject: Re: elog(FATAL) vs shared memory
Date: 2007-04-12 12:51:06
Message-ID: DC5995BC-9E10-46B0-8084-4607274391DC@decibel.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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(at)nasby(dot)net
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Gurjeet Singh 2007-04-12 12:55:14 Re: [HACKERS] [Fwd: Index Advisor]
Previous Message Merlin Moncure 2007-04-12 12:48:12 Re: Bug about column references within subqueries used in selects