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

Large Binary Objects Middleware

From: "Rodrigo Madera" <rodrigo(dot)madera(at)gmail(dot)com>
To: pgsql-performance(at)postgresql(dot)org
Subject: Large Binary Objects Middleware
Date: 2006-03-27 20:16:18
Message-ID: 3cf983d0603271216x6d4a4614ye6dc48e31e8b5cb6@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-performance
Hello to all on the list.

I have developed a product that sits between the database and an
application that handles the storage of large binary data.

The system is fast, but I'm feeling bad as to think that I have
completely reinvented the weel on this case.

You see, the engine does just stores the large data in "containers"
that are directly on the filesystem instead of going to the database
directly (since some of this list's members told me it would make the
database really slow to store the data directly).

So now I have a huge dilema as to continue this reinvention or use
direct large objects.

The database is holding large ammounts of digital video, and I am
wanting to put these directly into the database. What performance
guidelines would you all give seeing my position today?

Thanks for all your speed-up tips,
Rodrigo

Responses

pgsql-performance by date

Next:From: Mikael CarneholmDate: 2006-03-27 21:57:43
Subject: Re: count(*) performance
Previous:From: Guido NeitzerDate: 2006-03-27 19:43:43
Subject: Re: count(*) performance

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