Thanks for the great anwsers.
I recieved good answers.
I had not even started thinking about the normalization part of it yet.
I am not sure I understand the implications of the piping it to the insert
routine.
That sure would sound like a simple effective method.
respectfully,
Joseph
> -----Original Message-----
> From: pgsql-general-owner@postgresql.org
> [mailto:pgsql-general-owner@postgresql.org]On Behalf Of KuroiNeko
> Sent: Monday, April 02, 2001 9:10 AM
> To: pgsql-general@postgresql.org
> Subject: Re: [GENERAL] Log file to sql database
>
>
> > Anyone care to share suggestions on getting data from a running
> syslog
> > into
> > postgresql database?
>
> One way would be adding something like this to syslog.conf:
>
> <facility>.<priority> |/path/to/insert/routine
>
> However that might impose unwanted burden. Also, IIRC syslog
> keeps
> `routine' loaded so making sure it doesn't waste precious cycles while
> idle
> is up to you. This pipe would be always ready for reading, so
> select()
> might fail to work as desired.
> Another approach is to enhance log rotation program to add the records
> to
> the database. Depends on log rotation program :)
> YMMV, as always and good DB design for syslog is yet to be developed
> IMHO.
> On one hand it has to be normalised enough to eliminate repetitions, on
> the
> other hand, it needs to be simple and flexible to be able to adopt
> to
> various not-so-standard programs that use syslog.
> At least, facility, priority, timestamp, hostname and process (name
> and
> PID) are quite common.
>
>
> --
>
> LD$/G-$OAM$rJa$i$L
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
>
