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 159895
All versions of PostgreSQL. Add an additional version-specific tag like [postgresql-13] if that context is relevant.
0
votes
3
answers
1k
views
How can I improve the performance of this query?
I've tried to add an index on records.status, but the cardinality is so low (<5 unique values) a seq scan was still used.
The query:
select distinct "events".* from "events"
inner join (select "rec …
- 23
2
votes
1
answer
1k
views
Slow PostgreSQL query analysis, low memory usage, high writes
I'm having issues with the following query in PostgreSQL 10.5.
Using pg_activity while the query runs show that only ~400 MB of RAM is used. …
- 23