| From: | adey <adey11(at)gmail(dot)com> |
|---|---|
| To: | "Scott Marlowe" <smarlowe(at)g2switchworks(dot)com> |
| Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>, postgresql-l <postgresql-l(at)groups(dot)ittoolbox(dot)com> |
| Subject: | Re: Recycle error logs |
| Date: | 2006-07-18 01:00:41 |
| Message-ID: | 1c66bda80607171800r2b372148q4b4e1b6e4b83af42@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Many thanks to all of you that helped with this.
On 7/18/06, Scott Marlowe <smarlowe(at)g2switchworks(dot)com> wrote:
>
> On Sat, 2006-07-15 at 02:37, adey wrote:
> > Please advise if there is a way to start a fresh Postgresql error /
> > output log at regular intervals?
> > We are tuning a "new toproduction" system, so I have all the SQL
> > logged, but the file gets too big and cumbersome, so I'd like to start
> > a new one each morning without restarting Postgres.
>
> As mentioned previously, it's built into 8.0 and up. If you're stuck on
> a version before that, you can use apache's log rotator to do the job.
>
> Something like this:
>
> pg_ctl start | /usr/sbin/rotatelogs /logs/pgsql 86400
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dilipkumar | 2006-07-18 03:48:22 | Re: Restarting PostgreSQL |
| Previous Message | adey | 2006-07-18 00:50:44 | Tables not restored from V7.4 to v8.1.4 |