Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
Already on GitHub? Sign in to your account
Add an index to event_search #2218
Conversation
richvdh
added some commits
May 11, 2017
richvdh
assigned
erikjohnston
May 11, 2017
richvdh
added some commits
May 11, 2017
|
Is there a reason we make this more complicated and make it UNIQUE? |
does that actually make it materially more complicated? I'd argue |
It's probably be fine, I don't think UNIQUE is that much slower than non unique indices |
I'm struggling to imagine an implementation in which a unique index is not at least as fast as a non-unique one, for any given operation. |
richvdh
merged commit d648f65
into
develop
May 16, 2017
8 checks passed
richvdh
deleted the
rav/event_search_index
branch
May 16, 2017
Specifically an INSERT as the the DB would then need to check whether the unique constraint was violated or not. OTOH, that's probably not any worse than just updating the index anyway. |
richvdh commentedMay 11, 2017
also, add some more logging