From: Rodrigo Madera <rodrigo.madera@gmail.com>
To: pgsql-performance@postgresql.org
Subject: Large Binary Objects Middleware
Date: Mon, 27 Mar 2006 12:16:18 -0800
Message-ID: <3cf983d0603271216x6d4a4614ye6dc48e31e8b5cb6@mail.gmail.com> (raw)
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: rodrigo.madera@gmail.com
Subject: Re: Large Binary Objects Middleware
In-Reply-To: <3cf983d0603271216x6d4a4614ye6dc48e31e8b5cb6@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox