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

Re: Storing many big files in database- should I do it?

From: Guillaume Lelarge <guillaume(at)lelarge(dot)info>
To: Justin Graf <justin(at)magwerks(dot)com>
Cc: David Wall <d(dot)wall(at)computer(dot)org>, Postgres General Postgres General <pgsql-general(at)postgresql(dot)org>
Subject: Re: Storing many big files in database- should I do it?
Date: 2010-04-29 16:52:20
Message-ID: 4BD9B944.4090604@lelarge.info (view raw or flat)
Thread:
Lists: pgsql-general
Le 29/04/2010 18:45, Justin Graf a écrit :
> On 4/29/2010 12:07 PM, David Wall wrote:
>>
>>
>> Big downside for the DB is that all large objects appear to be stored 
>> together in pg_catalog.pg_largeobject, which seems axiomatically 
>> troubling that you know you have lots of big data, so you then store 
>> them together, and then worry about running out of 'loids'.
> Huh ???  isn't that point of using bytea or text datatypes.
> 
> I could have sworn bytea does not use large object interface it uses 
> TOAST or have i gone insane
> 

You're not insane :)

Put it another way: bytea values are not stored in the pg_largeobject
catalog.


-- 
Guillaume.
 http://www.postgresqlfr.org
 http://dalibo.com

In response to

Responses

pgsql-general by date

Next:From: Oliver Kohll - Mailing ListsDate: 2010-04-29 17:21:40
Subject: Re: Cumulative count (running total) window fn
Previous:From: Ozz NixonDate: 2010-04-29 16:49:08
Subject: Re: Performance and Clustering

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