Skip site navigation (1) Skip section navigation (2)

Re: Storing binary data.

From: Shridhar Daithankar <shridhar(at)frodo(dot)hserus(dot)net>
To: Jesper Krogh <jesper(at)krogh(dot)cc>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Storing binary data.
Date: 2004-08-11 15:12:50
Message-ID: 200408112042.50356.shridhar@frodo.hserus.net (view raw or flat)
Thread:
Lists: pgsql-performance
On Wednesday 11 Aug 2004 7:59 pm, Jesper Krogh wrote:
> The "common" solution, I guess would be to store them in the filesystem
> instead, but I like to have them just in the database it is nice clean
> database and application design and if I can get PostgreSQL to "not
> cache" them then it should be excactly as fast i assume.

You can normalize them so that a table contains an id and a bytea column only. 
Te main table will contain all the other attributes and a mapping id. That 
way you will have only the main table cached.

You don't have to go to filesystem for this, I hope.

HTH

 Shridhar

In response to

Responses

pgsql-performance by date

Next:From: Sanjay AroraDate: 2004-08-11 15:47:10
Subject: Re: Hardware upgrade for a high-traffic database
Previous:From: Jesper KroghDate: 2004-08-11 14:29:46
Subject: Storing binary data.

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group