Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Dangerous hint in the PostgreSQL manual
- From: Andrew Sullivan <ajs(at)crankycanuck(dot)ca>
- To: pgsql-admin(at)postgresql(dot)org
- Subject: Re: Dangerous hint in the PostgreSQL manual
- Date: Thu, 13 Dec 2007 16:49:47 -0500
On Wed, Dec 12, 2007 at 06:01:52PM +0100, Listaccount wrote: > BTW : How can one find out the application doing unused allocations? > What value of "ps" output to watch for? As far as I know, the only way to learn that is to use a debugger. If the OS knew this, it'd be able to shoot the misbehaving process instead of whatever it guesses on. A
- References:
- Dangerous hint in the PostgreSQL manual
- From: Listaccount
- Re: Dangerous hint in the PostgreSQL manual
- From: Andrew Sullivan
- Re: Dangerous hint in the PostgreSQL manual
- From: Listaccount
- Re: Dangerous hint in the PostgreSQL manual
- From: Andrew Sullivan
- Re: Dangerous hint in the PostgreSQL manual
- From: Listaccount
- Re: Dangerous hint in the PostgreSQL manual
- From: Andrew Sullivan
- Re: Dangerous hint in the PostgreSQL manual
- From: Listaccount
- Re: Dangerous hint in the PostgreSQL manual
- From: Andrew Sullivan
- Re: Dangerous hint in the PostgreSQL manual
- From: Listaccount
- Dangerous hint in the PostgreSQL manual
- Prev by Date: Re: reading pg_stat_activity view
- Next by Date: Re: reading pg_stat_activity view
- Previous by thread: Re: Dangerous hint in the PostgreSQL manual
- Next by thread: Re: Dangerous hint in the PostgreSQL manual
- Indexes: