At the site CQ Performance FAQ there is a recommendation to have not more than 200 child nodes for a parent node. I was really stunned reading this. Is this a problem for jackrabbit as well. And if so, how do you organize your 240000 PDFs to avoid problems. Ulrich Am 29.01.2013 um 14:55 schrieb <msl...@email.cz>:
> It is how Postgres stores (big) binary data. See http://www.postgresql.org/ > docs/9.2/static/storage-toast.html. It is set so when > you save binary data using db persistence manager. In this case binary data > are stored in db as binary fields. > > Marek > > -- > Marek Slama > msl...@email.cz > > > > ---------- Původní zpráva ---------- > Od: david.wery <david.w...@calysis.be> > Datum: 29. 1. 2013 > Předmět: PostgreSQL PersistenceManager disk space (pg_toast) > > "Hi the community, > > I'm currently importing lots of PDF to JackRabbit and I have a strange > behavior with the disk space usage (or I don't understand it). > > I'm using the following configuration : > > > While importing the PDF (240 000 in total), i have the PostgresQL database > xxx and the /var/xxx/repository/data folder growing at the same speed and > having +/- the same size. For example, for 23 000 documents imported, the > database size is 9.9 G and the /var/xxx/repository/data size is 9.9 G. > > Querying the database to get table size give me : > > > The full database size is consumed on the table pg_toast.pg_toast_408680. > Does someone have an idea on what is this table and it is used for ? > > Many thanks ! > > > > ----- > > > > > > > > David Wery > CTO @ Manex > Rue Wagner 127Belgique BE-4100 Boncelles Belgium > > Office : +32 4 330 37 33 Mobile : +32 497 50 53 20 > > david.w...@manex.biz www.manex.biz > > > Follow us! > > > > > > > -- > View this message in context: http://jackrabbit.510166.n4.nabble.com/ > PostgreSQL-PersistenceManager-disk-space-pg-toast-tp4657533.html > Sent from the Jackrabbit - Users mailing list archive at Nabble.com."=
