Search Results
Search type | Search syntax |
---|---|
Tags | [tag] |
Exact | "words here" |
Author |
user:1234 user:me (yours) |
Score |
score:3 (3+) score:0 (none) |
Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
Views | views:250 |
Code | code:"if (foo != bar)" |
Sections |
title:apples body:"apples oranges" |
URL | url:"*.example.com" |
Saves | in:saves |
Status |
closed:yes duplicate:no migrated:no wiki:no |
Types |
is:question is:answer |
Exclude |
-[tag] -apples |
For more details on advanced search visit our help page |
Results tagged with postgresql
Search options not deleted
user 260654
All versions of PostgreSQL. Add an additional version-specific tag like [postgresql-13] if that context is relevant.
0
votes
1
answer
50
views
In postgres, why does (5999.999999999999::float8)::numeric = 6000?
I've seen some related questions but none that gave a satisfying answer to this.
select
((5999.999999999999)::numeric) as num,
((5999.999999999999)::float8) as f64,
((5999.999999999999)::f …
1
vote
1
answer
174
views
Is there a way to tell Postgres to automatically give up on a plan and consider alternatives...
There seems to be a few situations in which Postgres considers an "on average slightly better" plan over a "more predictable plan"
The failure mode of which can be the following:
SELECT min(number) FR …
1
vote
2
answers
341
views
How can I make queries on skewed datasets more performant on Postgres
I have a seemingly simple query that's unfortunately extremely slow.
I believe that I know why it is slow, but not how to make it fast, so I'd like to see how this could be improved.
let's call the ta …