> Rick Otten hat am 12. Dezember 2015 um 01:55
> geschrieben:
>
>
> Why does it index scan when I use where, but not when I do a join?
difficult to say/guess because of anonymized names and not knowing the real
query. This one? http://explain.depesz.com/s/1es ?
All seqscans are fast, a seqsc
Why does it index scan when I use where, but not when I do a join?
On Fri, Dec 11, 2015 at 7:20 PM, Andreas Kretschmer wrote:
>
> > Rick Otten hat am 11. Dezember 2015 um 23:09
> > geschrieben:
>
> >
> > The query performance hit for sequence scanning isn't all that terrible,
> > but I'd rather
> Rick Otten hat am 11. Dezember 2015 um 23:09
> geschrieben:
>
> The query performance hit for sequence scanning isn't all that terrible,
> but I'd rather understand and get rid of the issue if I can, now, before I
> run into it again in a situation where it is crippling.
i think, you should
Ok, here is the first case where I select on the column:
http://explain.depesz.com/s/ECb
Here is the second case where I try a join:
http://explain.depesz.com/s/qIu
And here is the third case where I add a filter on the parent table:
http://explain.depesz.com/s/1es
The primary use
> Rick Otten hat am 11. Dezember 2015 um 21:40
> geschrieben:
>
>
> I do not know why if I blast a new index creation on the 20 or so children
> all at once some of them fail, but then if I go back and do a few at a time
> they all work. It has happened to me 3 times now, so I'm pretty sure I
On Fri, Dec 11, 2015 at 1:01 PM, Rick Otten wrote:
> The first thing I noticed, when creating indexes on the 20 or so partitions,
> was that if I create them too fast they don't all succeed. I have to do a
> few at a time, let them breathe for a few seconds, and then do a few more.
> I had been
I do not know why if I blast a new index creation on the 20 or so children
all at once some of them fail, but then if I go back and do a few at a time
they all work. It has happened to me 3 times now, so I'm pretty sure I'm
not imagining it.
What specifically in the explain analyze output tells y
Rick Otten wrote:
> I'm using PostgreSQL 9.5 Beta 2.
>
> I am working with a partitioned table set.
>
> The first thing I noticed, when creating indexes on the 20 or so partitions,
> was that if I create them too fast they don't all succeed. I have to do a few
> at a time, let them breathe for
I'm using PostgreSQL 9.5 Beta 2.
I am working with a partitioned table set.
The first thing I noticed, when creating indexes on the 20 or so
partitions, was that if I create them too fast they don't all succeed. I
have to do a few at a time, let them breathe for a few seconds, and then do
a few
