Hi Tom!
Yep, there are a large number of host_luid/log_luid combinations (there
are approximatly 5-10 hosts and 1-3 logs per system we are running).
Thanks for the recommended workaround, I'll have a try at it at some point
tomorrow.
Regards!
Ed
On Sat, 15 Jan 2005, Tom Lane wrote:
> Edmund D
Edmund Dengler <[EMAIL PROTECTED]> writes:
> "record_to_process_idx" unique, btree (host_luid, log_luid, luid) WHERE
> (error IS NULL)
> explain analyze
> select record
> from agent.record
> where host_luid = 3::bigint
> and log_luid = 2::bigint
> and error is null
> order by host_luid de
On Sat, Jan 15, 2005 at 04:00:03PM -0500, Edmund Dengler wrote:
> Greetings!
>
> I have a technical question concerning multi-column indexes and their
> implementation. I tried looking for the answr in the docs but couldn't
> find anything.
> I guess it breaks down to how these indexes are imple
Greetings!
I have a technical question concerning multi-column indexes and their
implementation. I tried looking for the answr in the docs but couldn't
find anything.
I have the following table:
eventlog=> \d agent.record
Table "agent.record"
Colu
On Wed, 10 Mar 1999, Rodney McDuff wrote:
Those do two different things. If you always plan using doing
lookups on both of those columns at the same time, it only makes sense to
do one index with both. If you rarely do, but do lots of lookups using
either, then do more than one index.
Hi
When you have a table with multiple columns and you want indexes on
them you can either
(a) create index table_idx on table using btree ( col1, col2, ..., col7);
or
(b) create index table_col1_idx on table using btree ( col1 );
create index table_col2_idx on table using btree (
