-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thu, 29 Nov 2007 11:58:36 -0500
Andrew Sullivan <ajs@crankycanuck.ca> wrote:
> On Thu, Nov 29, 2007 at 04:50:45PM +0000, 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 see how, but some have argued strongly. So I say, if
> there's a demand, I've no objection to an add-on product (which could
> be especially relevant if we get something like CPgAN); but not
> anything like additional extensions to the existing logging
> infrastructure (what is there is nice, because it provides things
> that the poastmaster alone may know; but additions would be gilding
> the lily, except with pyrites).
The only argument I have ever heard that seemed like a realistic issue
with using logrotate or syslog was tgl's. You can loose data in the log
when rotating if you aren't using the PostgreSQL logging facility.
Other than that I think our current logging situation is a bit
ridiculous. [1]
Joshua D. Drake
[1]
http://www.commandprompt.com/blogs/joshua_drake/2007/11/postgresql_logging_time_for_a_change/
>
> A
>
- --
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240
PostgreSQL solutions since 1997 http://www.commandprompt.com/
UNIQUE NOT NULL
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHTvEeATb/zqfZUUQRAn5gAKCEVbnJ3AND8uoxOyH10wMamgg76wCfUO9m
wKMFNGEyH25TFgAQe2xTuu8=
=DAHh
-----END PGP SIGNATURE-----
