On Thu, Nov 29, 2007 at 12:48:35PM -0500, Tom Lane wrote:
> Andrew Sullivan <[EMAIL PROTECTED]> writes:
> > The general tone in this thread sounds like, "I don't have time to
> > administer this; help me." Providing such help is a bad idea.
>
> Actually, can't it be solved easily enough with sui
Andrew Sullivan <[EMAIL PROTECTED]> writes:
> The general tone in this thread sounds like, "I don't have time to
> administer this; help me." Providing such help is a bad idea.
Actually, can't it be solved easily enough with suitable configuration
of the existing logging parameters? Just set th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 29 Nov 2007 11:58:36 -0500
Andrew Sullivan <[EMAIL PROTECTED]> wrote:
> On Thu, Nov 29, 2007 at 04:50:45PM +, Richard Huxton wrote:
> > Surely this is what logrotate and syslog-ng etc are for. This is a
> > sysadmin problem not a DBA prob
On Thu, Nov 29, 2007 at 04:50:45PM +, Richard Huxton wrote:
> Surely this is what logrotate and syslog-ng etc are for. This is a
> sysadmin problem not a DBA problem - any service can generate a lot of logs.
Yes. But some have complained those things aren't Postgres-centric enough.
I don't s
Andrew Sullivan wrote:
On Thu, Nov 29, 2007 at 04:20:30PM +, Simon Riggs wrote:
- pg_log file archiving when we reach a certain volume/number of logs
IMO, by the time we get that complicated, admins need to start doing some
work. That is, I think, work that should be nowhere near the main
As far as automatic archiving is concerned the easiest would be to provide
something similar to "archive_command" , however i can't imagine how the
second suggestion could be useful, that sounds like pretty dangerous to me.
On Nov 29, 2007 9:20 PM, Simon Riggs <[EMAIL PROTECTED]> wrote:
> On T
On Thu, Nov 29, 2007 at 04:20:30PM +, Simon Riggs wrote:
>
> - pg_log file archiving when we reach a certain volume/number of logs
IMO, by the time we get that complicated, admins need to start doing some
work. That is, I think, work that should be nowhere near the main
PostgreSQL code. If
On Thu, 2007-11-29 at 09:53 -0600, Abraham, Danny wrote:
> Recently an application endless loop crashed the PG server.
>
> I am looking for the safest way to limit the growth of the all the
> files in the “pg_log” directory,
>
> While still maintain reasonable period of log.
Sounds like we sh
what i do is setup a cron job which runs daily or every second day, creates
a tar.gz and copies them to a seperate location, and then another cron job
which clears up archives more than one month old. That seems to be the way
to go, i don't think you will find a postgresql.conf parameter which does
Hello
Recently an application endless loop crashed the PG server.
I am looking for the safest way to limit the growth of the all the files in
the “pg_log” directory,
While still maintain reasonable period of log.
Any suggestions?
Our current setup is:
#--
10 matches
Mail list logo
