Hi Jeff,
Thanks for clarifications!
In my case yes, it's just few blocks, but different ones every time I
change user_id value in my WHERE clause. When I change user_id - buffers
are no longer "shared hit" in EXPLAIN. This is a bit more worrying.
But if there is no easy fix - well, OK.
Best re
2014-10-16 14:04 GMT-03:00 Jeff Janes :
> On Thu, Oct 16, 2014 at 5:35 AM, Дмитрий Шалашов
> wrote:
>
>> Hi,
>>
>> lets imagine that we have some table, partitioned by timestamp field, and
>> we query it with SELECT with ordering by that field (DESC for example),
>> with some modest limit.
>> Let
On Thu, Oct 16, 2014 at 5:35 AM, Дмитрий Шалашов wrote:
> Hi,
>
> lets imagine that we have some table, partitioned by timestamp field, and
> we query it with SELECT with ordering by that field (DESC for example),
> with some modest limit.
> Lets further say that required amount of rows is found
Hi!
So this is not obviously normal, I guess?)
My version is 9.2.9, constraint_exclusion set to 'partition'.
# \d user_feed_master
Table "public.user_feed_master"
Column |Type |
Modifiers
+
Hello!
Le 2014-10-16 à 08:35, Дмитрий Шалашов a écrit :
> lets imagine that we have some table, partitioned by timestamp field, and we
> query it with SELECT with ordering by that field (DESC for example), with
> some modest limit.
> Lets further say that required amount of rows is found in the
Hi,
lets imagine that we have some table, partitioned by timestamp field, and
we query it with SELECT with ordering by that field (DESC for example),
with some modest limit.
Lets further say that required amount of rows is found in the first table
that query encounters (say, latest one).
I am just
