Re: Logspace not being freed up?
- From: John-Paul Stewart <jpstewart@xxxxxxxxxxxxxxxx>
- Date: Thu, 15 Dec 2005 11:53:33 -0500
bart770@xxxxxxxxx wrote:
I know for sure that the Postgres process is keeping the logs open because when I kill the process(es) all reserved hdd space is given back to me. But I don't like to kill postgres to free the space. It would mean that the website which is depending on it will be offline for some time, which is unacceptable to me :)
Use 'kill -HUP' to send it SIGHUP which is by convention the way to tell daemons to close/reopen log files and reload config files. You don't kill and restart the process. You signal it!
.
- Follow-Ups:
- Re: Logspace not being freed up?
- From: bart770
- Re: Logspace not being freed up?
- References:
- Logspace not being freed up?
- From: bart770
- Re: Logspace not being freed up?
- From: Shmuel (Seymour J.) Metz
- Re: Logspace not being freed up?
- From: bart770
- Logspace not being freed up?
- Prev by Date: Re: Advantages of 64-bit Installation?
- Next by Date: Re: shutdown hangs
- Previous by thread: Re: Logspace not being freed up?
- Next by thread: Re: Logspace not being freed up?
- Index(es):