That did it! I certainly should have been able to figure that out on my
own. Thanks for the help!
Unfortunately, I'm still looking at rather slow queries across my entire
dataset. I might wind up having to find another solution.
Gideon.
On Wed, Aug 12, 2015 at 6:29 PM Tom Lane wrote:
> Gideon
Gideon Dresdner writes:
> I've created a small dump of my database that recreates the problem. I hope
> that this will help recreate the problem. It is attached. I'd be happy to
> hear if there is an easier way of doing this.
Ah. Now that I see the database schema, the problem is here:
regressi
I've created a small dump of my database that recreates the problem. I hope
that this will help recreate the problem. It is attached. I'd be happy to
hear if there is an easier way of doing this.
To rebuild the database:
- create a database
- run from the commandline `$ psql database-name < 1000ge
What's a good way for me to create a self-contained test case. AFAIU the
only way to make these test cases more self-contained would be to inline
the second table and its index. How do you create an index to an inlined
table of values?
Or perhaps I could send over a dump of a subset of the data?
Gideon Dresdner writes:
> I had a discussion on IRC today with RhodiumToad regarding optimizing a
> specific query. We didn't manage to figure out how to get postgres to hit a
> GIST index.
FWIW, I couldn't reproduce the described behavior. Can you provide a
self-contained test case? Are you su
Greetings,
I had a discussion on IRC today with RhodiumToad regarding optimizing a
specific query. We didn't manage to figure out how to get postgres to hit a
GIST index.
The bigger picture is that I am trying to do some bioinformatics and
thought that postgres would be a great way of getting the
