From: | Jochem van Dieten <jochemd(at)oli(dot)tudelft(dot)nl> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: slow queries on large syslog table |
Date: | 2001-12-14 00:40:49 |
Message-ID: | 3C194A91.8000309@oli.tudelft.nl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
colm ennis wrote:
>
> im using a postgresql db to store cisco syslogs which are pumped in by
> msyslog.
>
> my postgresql is version 7.1.3, is running on freebsd 4.3 and is the
> standard ports install.
>
> my tables are :
> create table syslog_table (stimestamp timestamp,shostid integer,sciscomsgid
> integer, smsg text);
> create table ciscomsg_table (sciscomsgid serial,sciscomsg varchar(128));
> create table host_table (shostid serial,shost varchar(128));
>
> ive created a trigger on insertion to syslog_table which extracts ciscomsg,
> and updates the other two tables.
So what is in the smsg field if the ciscomsg is extracted by the trigger
and placed in a separate table? Something so big you really need a text
field?
Jochem
From | Date | Subject | |
---|---|---|---|
Next Message | Bob Jones | 2001-12-14 00:50:12 | Working on "SELECT * WHERE numeric_col = 2001.2" problem? |
Previous Message | Jochem van Dieten | 2001-12-14 00:38:31 | Re: slow queries on large syslog table |