RE: [QUESTIONS] Identity Crisis

Поиск
Список
Период
Сортировка
От Jackson, DeJuan
Тема RE: [QUESTIONS] Identity Crisis
Дата
Msg-id F10BB1FAF801D111829B0060971D839F26D93D@dal_cps.cpsgroup.com
обсуждение исходный текст
Ответы Re: [HACKERS] RE: [QUESTIONS] Identity Crisis  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
Forwarded to HACKERS.

> -----Original Message-----
> From:    Len Morgan [SMTP:len-morgan@xroadstx.com]
> Sent:    Saturday, May 02, 1998 8:21 AM
> To:    pgsql-questions@postgreSQL.org
> Subject:    [QUESTIONS] Identity Crisis
>
> I am running 6.3.2 at one of my client's sites that normally has 5
> users
> connected.  The problem I run into is that after a couple of days, I
> end
> up with as many as 12-15 postgres backends running on the server.  The
> users are encountering a bug in the code and then closing the window
> and
> restarting the program which never closes down the connection to the
> back end.  My question is this: Is there a way to identify on the line
> which starts up the backends, which host is starting it?  In other
> words, if I do ps -ax on the server, can I have an ip address or host
> name show up to let me know which host is connected to which backend?
> This will not entirely solve my problem, but it will let me know which
> user I need to educate about the proper way to work around the program
> bug.  Currently, I just kill the processes off one by one.  If
> somebody
> calls me in the next five minutes or so, it was a "live" one.
> Otherwise, nobody missed it.  Also, if I send -SIGTERM to the
> individual
> backend's pid, will this properly clean up any memory that is in use?
>
> Thanks,
>
> len morgan
>
> --
> Official WWW Site: http://www.postgresql.org
> Online Docs & FAQ: http://www.postgresql.org/docs
> Searchable Lists: http://www.postgresql.org/mhonarc

В списке pgsql-hackers по дате отправления:

Предыдущее
От: "Jackson, DeJuan"
Дата:
Сообщение: RE: [QUESTIONS] Transaction Logs
Следующее
От: "Jackson, DeJuan"
Дата:
Сообщение: RE: [QUESTIONS] Insert Errors