-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
A separate table just for that one column? Would that really help,
given that I'd have to add the foreign key dataset_id to the related
table? How does splitting activity across dataset and, say,
dataset_counts help things?
Well, it
Tony Cebzanov wrote:
The throughput of the first batch of 1,000 is diminished, but still
tolerable, but after 10,000 inserts, it's gotten much worse. This
pattern continues, to the point where performance is unacceptable after
20k or 30k inserts.
To rule out the performance of the trigger
On 04/02/2009 03:32 PM, Tom Lane wrote:
Tony Cebzanov tony...@andrew.cmu.edu writes:
What I want to do is update the assoc_count field in the dataset table
to reflect the count of related records in the assoc field. To do so, I
added the following trigger:
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
I was looking to speed up a count(*) query
A few things spring to mind:
1) Use a separate table, rather than storing things inside of
dataset itself. This will reduce the activity on the dataset table.
2) Do you really need bigint for the
