> On Fri, 22 Feb 2008, Moritz Onken wrote:
>> I thought of doing all the inserts without having an index and without
>> doing the check whether the row is already there. After that I'd do a
>> "group by" and count(*) on that table. Is this a good idea?
> That sounds like the fastest way to do it, certainly.
Yeah I would load the data into a temp 3-column table and then
INSERT INTO mydatatable SELECT w1,w2,w3,count(*) GROUP BY w1,w2,w3
CREATE UNIQUE INDEX idx_unique_data ON mydatatable (w1,w2,w3)
if you plan to continue adding to and using the data.
If this is to be an ongoing data collection (with data being added
slowly from here) I would probably setup a trigger to update the count
I am also wondering about the ordering and whether that matters.
Can you have "he", "can", "drink" as well as "drink", "he", "can"
and should they be considered the same? If so you will need a different
pgSQL (at) Sheeky (dot) Biz
Get Sheeky @ http://Sheeky.Biz
In response to
pgsql-performance by date
|Next:||From: Moritz Onken||Date: 2008-02-23 09:07:18|
|Subject: Re: store A LOT of 3-tuples for comparisons|
|Previous:||From: Dean Gibson (DB Administrator)||Date: 2008-02-23 01:48:48|
|Subject: Re: Q on views and performance|