Re: Ready for Beta ... ?

From: Andreas Pflug <pgadmin(at)pse-consulting(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Ready for Beta ... ?
Date: 2004-08-08 23:03:25
Message-ID: 4116B13D.7070609@pse-consulting.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> "Marc G. Fournier" <scrappy(at)postgresql(dot)org> writes:
>
>>Hate to ask, but can someone summarize what it is that is being
>>"discussed" here? Andreas' post about 'size triggering' is what drew my
>>eye, but I think I missed the central point :(
>
>
> Andreas wants database users to be
> able to force it to switch to a new log file on demand.

superuser only, of course.

> I don't think the latter is a particularly good idea for a number of
> reasons, but probably the main one is that I don't think users should be
> directly fooling with the server logs.

This is a bit contradictionary. pgsql allows any superuser to shoot
himself into his foot (citation: TGL) in many places, e.g. "delete from
pg_class". He may delete logfiles while in use, but not trigger the
rotation in an official way, which doesn't seem particularly harmful
(fooling with log_rotation_age and sighup would be a dubious workaround).

Regards,
Andreas

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2004-08-08 23:26:49 Add Missing From?
Previous Message Josh Berkus 2004-08-08 22:30:39 Error-out on compiling current CVS: preproc