From: | Yambu <hyambu(at)gmail(dot)com> |
---|---|
To: | Holger Jakobs <holger(at)jakobs(dot)com> |
Cc: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
Subject: | Re: current log file removal |
Date: | 2020-11-26 14:46:46 |
Message-ID: | CALhHtcBDudz_o3g2P48Rzh=qjWj6=h9=PxNpOO54M6_H2oQRpg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hi
When I renamed log file, there was no new one created, do I need to reload
postgres?
regards
On Thu, Nov 26, 2020 at 4:03 PM Holger Jakobs <holger(at)jakobs(dot)com> wrote:
> The ordinary log rotation should do.
>
> These are the default settings (therefore commented with a # in
> postgresql.conf):
>
> #log_rotation_age = 1d # Automatic rotation of logfiles
> will
> # happen after that time. 0
> disables.
> #log_rotation_size = 10MB # Automatic rotation of logfiles
> will
> # happen after that much log
> output.
> # 0 disables.
>
> So your log files will not exceed 10 MB.
>
> Of course, you can to this manually as well. Just rename the current
> logfile, a new one will be created.
>
> Then gzip or bzip2 or xz the old one.
>
> Am 26.11.20 um 14:40 schrieb Yambu:
> > Hi
> >
> > How can I safely remove the log file that is being used currently and
> > zip it without interfering with the postgres server?
> >
> > We are running out of space on the server and the logs are eating a
> > lot of space, we need to zip them without first stopping the server.
> >
> > regards
>
> --
> Holger Jakobs, Bergisch Gladbach, Tel. +49-178-9759012
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2020-11-26 14:49:28 | Move base directory to different location |
Previous Message | Paul Förster | 2020-11-26 14:37:06 | Re: Move base directory to different location |