Hey Manos,
2011/3/16 Manos Karpathiotakis
> Let me explain a few things about our dataset. We are using a system named
> Sesame [1] that stores and queries RDF data. In our case, it uses Postgres
> as a relational backend. In RDF, data are triples. Here is an example of an
> RDF triple:
>
> ex:P
Let me explain a few things about our dataset. We are using a system named
Sesame [1] that stores and queries RDF data. In our case, it uses Postgres
as a relational backend. In RDF, data are triples. Here is an example of an
RDF triple:
ex:Postgres rdf:type ex:RDBMS
Triples are stored in Postgre
Manos Karpathiotakis writes:
> Hi all,
> I am using postgres 9.0 under CentOS 5.5 (Dual Xeon Quad Core @ 2,44 GHz,
> 64GB RAM, 2TB RAID 5). In my case, postgres is used as a backend for the RDF
> store Sesame.
> I am trying to store a dataset that consists of approximately 900.000.000
> insertions
Hi all,
I am using postgres 9.0 under CentOS 5.5 (Dual Xeon Quad Core @ 2,44 GHz,
64GB RAM, 2TB RAID 5). In my case, postgres is used as a backend for the RDF
store Sesame.
I am trying to store a dataset that consists of approximately 900.000.000
insertions (organized in either 10 tables, or in an
William Yu <[EMAIL PROTECTED]> writes:
> Benjamin Arai wrote:
>> What is the current maximum number of tables per database? Also, does
>> having more tables slow down performance in any way?
> For most cases, the answer is no. However, once you get near 6 figure
> table counts, pg_catalog ends
Benjamin Arai wrote:
What is the current maximum number of tables per database? Also, does
having more tables slow down performance in any way?
For most cases, the answer is no. However, once you get near 6 figure
table counts, pg_catalog ends up being pretty massive. The problem is
that the
What is the current maximum number of tables per database? Also, does
having more tables slow down performance in any way?
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
