Search Postgresql Archives
R: Search on very big (partitioned) table
[
Date Prev
][
Date Next
][
Thread Prev
][
Thread Next
][
Date Index
][
Thread Index
]
Subject
: R: Search on very big (partitioned) table
From
: Job <Job@xxxxxxxxxxxxxxxxxxxx>
Date
: Tue, 21 Feb 2017 22:49:36 +0100
Accept-language
: it-IT
Acceptlanguage
: it-IT
Cc
: "pgsql-general@xxxxxxxxxxxxxx" <pgsql-general@xxxxxxxxxxxxxx>
In-reply-to
: <CAFU+HBwd7wyV34_H030hqZAcXrebRwfDLDEt2hcpXzf=c+thBg@mail.gmail.com>
References
: <
88EF58F000EC4B4684700C2AA3A73D7A08054EACC730@W2008DC01.ColliniConsulting.lan
> <
CAMjNa7ffVJHFrT6Rgc-74r-MLZm1hGWkQucgfmtBuPfvL-0_Mw@mail.gmail.com
> <CAFU+HBwd7wyV34_H030hqZAcXrebRwfDLDEt2hcpXzf=c+thBg@mail.gmail.com>
Hi Sushant,
i think the problem is that we miss check constraints.
We will implement asap....
For the moment thank you to everybody for the excellent support!
/F
[
Date Prev
][
Date Next
][
Thread Prev
][
Thread Next
][
Date Index
][
Thread Index
]
References
:
Search on very big (partitioned) table
From:
Collini, ColliniConsulting.it
Re: Search on very big (partitioned) table
From:
Adam Brusselback
Re: Search on very big (partitioned) table
From:
Sushant Pawar
Prev by Date:
bloat indexes - opinion
Next by Date:
R: R: Slow queries on very big (and partitioned) table
Previous by thread:
Re: Search on very big (partitioned) table
Next by thread:
Move rows from one database to other
Index(es):
Date
Thread
[Index of Archives]
[Postgresql Jobs]
[Postgresql Admin]
[Postgresql Performance]
[Linux Clusters]
[PHP Home]
[PHP on Windows]
[Kernel Newbies]
[PHP Classes]
[PHP Books]
[PHP Databases]
[Postgresql & PHP]
[Yosemite]
