On 18/03/2017 01:22, Adrian Klaver wrote:
On 03/17/2017 06:07 PM, Martin F wrote:
Hi,
I just started last week to build postgresql from source. (So this may
well be something I did wrong on my side)
Do you really want to build the latest dev version?
Yes, I want the latest, and I understand
Hi,
I just started last week to build postgresql from source. (So this may
well be something I did wrong on my side)
I am on branch master
Revision: f7819baa618c528f60e266874051563ecfe08207
Date: 17/03/2017 18:58:06
I did build with
make clean distclean
./configure --prefix=/deploys/postg
On 03/03/2017 17:33, Tom Lane wrote:
Martin F writes:
The select with filter choose an IMHO better plan
Index Only Scan using tbl_foo_date on public.tbl_foo
But the bigger picture here, which would become more obvious if you were
working with a non-toy amount of data, is that you're a
On 03/03/2017 17:33, Tom Lane wrote:
Martin F writes:
Index Cond: (tbl_foo.id IS NOT NULL)
only "id" is the pk, and declared "not null".
So why this index condition?
You're right that we could observe that the NOT NULL is implied by a table
constraint and drop it,
for the "where" part)
To check this I tried
explain analyze verbose select min(created_at), min(id) filter(where
created_at >= '2017-01-15') from tbl_foo;
and it gives an index only as well.
Out of interest, anyone with 9.6.2, does it yield the same results?
On 03/03/2
Hi.
I am new, and not sure which mailinglist this should go to, so I start
with the general list. (please advice, if I should send this to a more
specific list)
This is tested with postgresql 9.5.5 (Maybe someone can confirm, if it
is the same with later versions, saving me the work to upgrade
