John Papandriopoulos writes:
> I've found that a k-ary table inheritance tree works quite well to
> reduce the O(n) CHECK constraint overhead [1] in the query planner
> when enabling partition constraint exclusion.
Um ... you mean you're creating intermediate child tables for no reason
except to
Hi everyone,
I've been trialling different inheritance schemes for partitioning to a large
number of tables. I am looking at ~1e9 records, totaling ~200GB.
I've found that a k-ary table inheritance tree works quite well to reduce the
O(n) CHECK constraint overhead [1] in the query planner when
Markus Schulz wrote:
> i have a big performance problem
> [joining two complex views for reporting]
What version of PostgreSQL is this? How is PostgreSQL configured?
(The postgresql.conf file with all comments removed is good.)
-Kevin
--
Sent via pgsql-performance mailing list (pgsql-p
On Nov 26, 2010, at 2:30 PM, Greg Smith wrote:
>
> In addition to the memory issues, there's also thread CPU scheduling
> involved here. Ideally the benchmark would pin each thread to a single
> core and keep it there for the runtime of the test, but it's not there
> yet. I suspect one sour
On Thu, Nov 18, 2010 at 5:10 AM, Uwe Bartels wrote:
> I'm experiencing extremely different response times for some complex pgsql
> functions. extremly different means from 20ms - 500ms and up to 20s.
> I have to say that the complete database fits in memory (64GB).
> shared_buffers is set to 16GB.
I've developed PostBIX, a multithread daemon to monitor Postgres SQL fully
integrated with zabbix, released under GPL V.3, and written in java.
I hope people can find this post useful
everyone can download Postbix from:
http://www.smartmarmot.com
sorces are available on sourceforge such as a bina
