Hello all,
Just wondering if there is anything else I can provide to help figure this
out.
One thing I did notice, is there is a discussion about "invisible indexes"
going on, which seems that if it was implemented, would be one way to "fix"
my problem:
https://www.postgresql.org/message-id/flat/e
Alright, the first two attempts to reply to this thread I don't believe
worked, likely due to the attachment size. Hoping this time it does...
> > Self contained examples do wonders
> Good point, will work on that and post once I have something usable.
Finally got around to making a self containe
> Self contained examples do wonders
Good point, will work on that and post once I have something usable.
Adam,
I think the first thing to do is to make hackers aware of the specifics of
which indexes are being used etc so that the planner could be taught how to
use better ones.
Self contained examples do wonders
Dave Cramer
da...@postgresintl.com
www.postgresintl.com
On 11 April 2018 at 01:59, Ad
Just wondering if anyone has any thoughts on what I can do to alleviate
this issue?
I'll kinda at a loss as to what to try to tweak for this.
Hey all,
I'm using Postgres 10.3
6 core VM with 16gb of ram
My database schema requires a good bit of temporal data stored in a
few my tables, and I make use of ranges and exclusion constraints to
keep my data consistent.
I have quite a few queries in my DB which are using a very sub-optimal
inde
