Reputation
Top tag
Next privilege 200 Rep.
See reduced ads
Badges
8
Newest
 Caucus
Impact
~2k people reached

  • 0 posts edited
  • 0 helpful flags
  • 4 votes cast
Aug
3
awarded  Caucus
May
12
awarded  Popular Question
Apr
9
accepted How to correctly use PostgreSQL to limit multiple and/or concurrent executions of a task
Apr
7
asked How to correctly use PostgreSQL to limit multiple and/or concurrent executions of a task
Apr
7
accepted How much should I care about prepared statements for simple queries?
Sep
26
asked How much should I care about prepared statements for simple queries?
Sep
24
awarded  Autobiographer
May
13
awarded  Critic
May
13
accepted Query improvements without UNION
May
12
comment Query improvements without UNION
Sure, I'm just trying to understand what is the best approach. Considering this is one of the most critical query and those tests where done on a very few records (whereas an user can have thousands of them), I'm taking the time to learn more about writing efficient queries.
May
12
comment Query improvements without UNION
The UNION seems to be the more efficient. Does this surprise you? gist.github.com/weppos/d552d978d604fbecd917
May
12
comment Query improvements without UNION
Yes, when the records had 1 ore more memberships, the same record was returned multiple times.
May
12
comment Query improvements without UNION
According to techonthenet.com/sql/exists.php the EXISTS statement is very inefficient. Does this mean this query is less efficient than UNION?
May
12
asked Query improvements without UNION
Oct
29
awarded  Scholar
Oct
29
awarded  Supporter
Oct
29
accepted Unexpected Seq Scan when doing query against boolean with value NULL
Oct
29
comment Unexpected Seq Scan when doing query against boolean with value NULL
Brilliant answer, thank you Erwin. I'm sad I can't upvote it twice.
Oct
26
awarded  Editor
Oct
26
revised Unexpected Seq Scan when doing query against boolean with value NULL
added 117 characters in body; edited tags