From: Theodore Petrosky <tedpet5@yahoo.com>
To: Andrei Bintintan <klodoma@ar-sd.net>
To: pgsql-sql@postgresql.org
Subject: Re: not really SQL but I need info on BLOBs
Date: Thu, 6 May 2004 04:46:22 -0700 (PDT)
Message-ID: <20040506114622.26803.qmail@web41007.mail.yahoo.com> (raw)
In-Reply-To: <004401c4332a$cee69f00$0b00a8c0@forge>
Thanks for the reply. Are there (in your opinion)
reasons why you would choose to store the images in
the db? My feelings are that it comes down to access.
If I store the images in the db, my only access to
these images is to retrieve the image do some work on
it and reupload it. If I store the image as a file and
link to it, I can edit the image to my hearts content
by mounting the volume and opening it in an image
editor and saving. there is nothing more to do.
archiving and backups are easier also. my tape system
talks to my server and backs up the images. I believe
it would be easier to recover from a problem.
in your solution, how do you retrieve your image? do
you need to mount the volume where the images live? I
guess I am asking "If your user/client queries the db
for an image, they may want to view it? How do you
send them the data?"
I am working on a project where the IT department is
pushing really hard to have all the images in the db.
I don't know what the agenda is. I am hopeful to come
up with reasons either why this is good or not good.
Thanks,
Ted
--- Andrei Bintintan <klodoma@ar-sd.net> wrote:
> I suggest to store the images on the disc and write
> in the db only the path.
> I am using the same solution. The only problem is
> that I have to make the
> backups separately(in my case). Also this helps more
> in accessing the
> images, you don't have to access for each image the
> database, you just have
> to get the file path.
>
> Think also at the dump size of the database (with
> blobs). (if you have 100GB
> of photos..the dump will be also that big)
>
> I never tied to put the database on 2 disks, I read
> somewhere that is
> possible but I never tried it. In my situation I
> don't need this, because
> the size of the DB is not quite that big. But for
> the photos we will use
> more discs (we are not using 2 yet) and there is no
> difference in this case
> how many discs you use, because in the DB you store
> only the path.
>
> I see it this way more simple, maybe other have
> other opinions.
>
> Best regards,
> Andy.
>
> ----- Original Message -----
> From: "Theodore Petrosky" <tedpet5@yahoo.com>
> To: <pgsql-sql@postgresql.org>
> Sent: Wednesday, May 05, 2004 6:10 PM
> Subject: [SQL] not really SQL but I need info on
> BLOBs
>
>
> > Hi,
> >
> > I am starting a new project where I need to store
> a
> > lot of tiff images. So the question beckons...
> which
> > is better (not correct)?
> > store a blob in the database and let the db manage
> the
> > data or
> > store the image in a directory and store the path
> to
> > the data in the db.
> >
> > What are your opinions? Is one method better than
> the
> > other or are there simply different trade offs?
> >
> > If I store the tiff on the computer and only store
> the
> > path in the database it would be easier to add
> more
> > disk space to the computer without any changes to
> the
> > db. Also, there would be 'virtually' unlimited
> storage
> > space (only limited by the OS)
> >
> > However, it looks like it would be easier to
> create a
> > connection to the database to access the blobs.
> >
> > I would love to hear not just what others have
> done
> > but why they did it?
> >
> > Thanks for listening...
> >
> > BTW, I really like the zeroconf (rendezvous)
> support
> > in postgresql.
> >
> > Ted
> >
> >
> >
> >
> > __________________________________
> > Do you Yahoo!?
> > Win a $20,000 Career Makeover at Yahoo! HotJobs
> >
> http://hotjobs.sweepstakes.yahoo.com/careermakeover
> >
> > ---------------------------(end of
> broadcast)---------------------------
> > TIP 8: explain analyze is your friend
> >
>
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please
> send an appropriate
> subscribe-nomail command to
> majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
__________________________________
Do you Yahoo!?
Win a $20,000 Career Makeover at Yahoo! HotJobs
http://hotjobs.sweepstakes.yahoo.com/careermakeover
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-sql@postgresql.org
Cc: tedpet5@yahoo.com, klodoma@ar-sd.net
Subject: Re: not really SQL but I need info on BLOBs
In-Reply-To: <20040506114622.26803.qmail@web41007.mail.yahoo.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