Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id F24369FB9CA for ; Sat, 21 Apr 2007 04:32:12 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 22448-05 for ; Sat, 21 Apr 2007 04:32:06 -0300 (ADT) X-Greylist: delayed 00:05:02.153933 by SQLgrey-1.7.4 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.174]) by postgresql.org (Postfix) with ESMTP id E34319FB9E4 for ; Sat, 21 Apr 2007 04:32:08 -0300 (ADT) Received: from [84.161.54.135] (helo=[127.0.0.1]) by mrelayeu.kundenserver.de (node=mrelayeu0) with ESMTP (Nemesis), id 0MKwh2-1Hf9zs2FMq-0006PM; Sat, 21 Apr 2007 09:27:05 +0200 Message-ID: <4629BCC7.1090900@cech-privat.de> Date: Sat, 21 Apr 2007 09:27:03 +0200 From: Ulrich Cech User-Agent: Thunderbird 2.0.0.0 (Windows/20070326) MIME-Version: 1.0 CC: pgsql-performance@postgresql.org Subject: Re: Large objetcs performance References: <26551fb50704040703n75d9b8d9p7ab4bf11109dfe63@mail.gmail.com> In-Reply-To: <26551fb50704040703n75d9b8d9p7ab4bf11109dfe63@mail.gmail.com> Content-Type: multipart/alternative; boundary="------------020304050302050400020902" X-Provags-ID: V01U2FsdGVkX19cVBC2j7bQxQu5v0nRGEFZuZoEhXvtUH5ZEAU DbmEeYoNWFZhllrILpfIWTUdcLNt0dPEN5lxa50sv2+f2NCmWP olNSd+cFWqR6hO/o2HSSw== X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200704/381 X-Sequence-Number: 24258 This is a multi-part message in MIME format. --------------020304050302050400020902 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hello Alexandre, I developed a relative simple "file archive" with PostgreSQL (web application with JSF for user interface). The major structure is one table with some "key word fields", and 3 blob-fields (because exactly 3 files belong to one record). I have do deal with millions of files (95% about 2-5KB, 5% are greater than 1MB). The great advantage is that I don't have to "communicate" with the file system (try to open a directory with 300T files on a windows system... it's horrible, even on the command line). The database now is 12Gb, but searching with the web interface has a maximum of 5 seconds (most searches are faster). The one disadvantage is the backup (I use pg_dump once a week which needs about 10 hours). But for now, this is acceptable for me. But I want to look at slony or port everything to a linux machine. Ulrich --------------020304050302050400020902 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hello Alexandre,

<
We have an application subjected do sign documents and store them somewhere.>

I developed a relative simple "file archive" with PostgreSQL (web application with JSF for user interface). The major structure is one table with some "key word fields", and 3 blob-fields (because exactly 3 files belong to one record). I have do deal with millions of files (95% about 2-5KB, 5% are greater than 1MB).
The great advantage is that I don't have to "communicate" with the file system (try to open a directory with 300T files on a windows system... it's horrible, even on the command line).

The database now is 12Gb, but searching with the web interface has a maximum of 5 seconds (most searches are faster). The one disadvantage is the backup (I use pg_dump once a week which needs about 10 hours). But for now, this is acceptable for me. But I want to look at slony or port everything to a linux machine.

Ulrich --------------020304050302050400020902--