|
|
|
|
|
|
by Something1234
1612 days ago
|
|
|
count(*) is always going to be slow. They don't store the number of live tuples, just an estimate so it's a full table scan. The secret is to use indexes to get down to a small bit that you care about. If you're filtering on 3 columns, the goal is to get the index to wipe out at least half the results you don't care about and so on and so forth. A 130M record table with no indexes is going to be crazy slow. Although if all you need are primary key updates, then that's the way to go. |
|
|