Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id D9D09632325 for ; Wed, 7 Apr 2010 11:01:19 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 56981-02 for ; Wed, 7 Apr 2010 14:01:08 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from smtp.domeneshop.no (smtp.domeneshop.no [194.63.248.54]) by mail.postgresql.org (Postfix) with ESMTP id 58187632315 for ; Wed, 7 Apr 2010 11:01:09 -0300 (ADT) Received: from [194.237.103.50] (helo=charliex.local) by smtp.domeneshop.no with esmtpa (Exim 4.71) (envelope-from ) id 1NzVoX-0003Bq-Jy; Wed, 07 Apr 2010 16:01:05 +0200 Message-ID: <4BBC9020.8090209@blogg.se> Date: Wed, 07 Apr 2010 16:01:04 +0200 From: =?UTF-8?B?Um9iZXJ0IEdyYXZzasO2?= Reply-To: robert@blogg.se Organization: Blogg Esse AB User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; sv-SE; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4 MIME-Version: 1.0 To: s.borse@direction.biz CC: pgsql-admin@postgresql.org Subject: Re: Handling of images via Postgressql References: <1270644614.2390.44.camel@dss-052.dsslp.com> In-Reply-To: <1270644614.2390.44.camel@dss-052.dsslp.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.001 tagged_above=-10 required=5 tests=BAYES_50=0.001 X-Spam-Level: X-Archive-Number: 201004/120 X-Sequence-Number: 34214 Suresh Borse skrev 2010-04-07 14.50: > > > How does PostGreSQL perform in case we have to store and use huge no of > images: > > Eg 4000 – 10000 images, each approx 2 MB size. > > > > The Questions that we have are: > > How do we handle such huge no of images so that the application does not > slow down? > > How does PostGreSQL use caching? In case of images does it cache? > > Do you suggest having the images in a different database by itself? I'd suggest storing meta information in PostgreSQL and the images in the filesystem. Regards, roppert > > > > Regards, > > Suresh >