Reputation
394
Top tag
Next privilege 500 Rep.
Access review queues
Badges
1 6
Newest
 Nice Answer
Impact
~2k people reached

Oct
31
awarded  Nice Answer
Sep
24
awarded  Autobiographer
Jul
23
comment How to avoid the SORT operation in SQL query that contains ORDER_BY condition?
Side-node: It's not a PostgreSQL limitation. OFFSET is bad in any database. Also: the solution shown in the slides is generally applicable to all databases (that's why I renamed the slides "Pagination done the right way"). Nevertheless, PostgreSQL is the only DB with proper row-values support which makes the "seek method" easy to implement. And thanks for linking my slides :)
Jan
21
awarded  Custodian
Jan
21
reviewed Approve why would rebuild index reduce btree leaf numbers
Jan
21
answered why would rebuild index reduce btree leaf numbers
Jan
20
comment Why is multiple independent index always better than concatenated index
@JürgenStrobel If you think so, prove it.
Jan
20
comment Why is multiple independent index always better than concatenated index
@JürgenStrobel sorry, I just don't see your argument. I'm talking about two facts: (1) one index lookup if faster than two; (2) combining the result of two index lookups needs resources too.
Jan
20
comment Why is multiple independent index always better than concatenated index
@JürgenStrobel Have you read the linked article? use-the-index-luke.com/sql/where-clause/searching-for-ranges/… Sure there are exceptions, but for the majority it is clearly better.
Jan
20
answered Why is multiple independent index always better than concatenated index
May
7
awarded  Yearling
Apr
9
answered Should I separate frequently updated columns?
Feb
3
awarded  Critic
Nov
17
awarded  Teacher
Nov
15
answered Are these good indexing guidelines?
Aug
15
awarded  Supporter