Re: Storing small image files

From: Eduardo Morras <emorrasg(at)yahoo(dot)es>
To: pgsql-general(at)postgresql(dot)org
Cc: nelsongreen84(at)gmail(dot)com
Subject: Re: Storing small image files
Date: 2013-05-10 07:59:17
Message-ID: 20130510095917.76af5ea4cb8fb9c6021c61ff@yahoo.es
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


Hi Nelson. I worked with images and Postgresql, and want to add some comments:

On Thu, 9 May 2013 13:40:15 -0500
Nelson Green <nelsongreen84(at)gmail(dot)com> wrote:
> OK, this is kind of convoluted, but I got a couple of test cases that work
> for me. The steps to make the first one are below.
>
> First I took one of the photos and shrunk it real small using GIMP.

If you want to manipulate images automatically, don't use GIMP, use ImageMagick(for shell scripts) or OpenCV(for C sourcecode)

> Then I
> manually converted that to a base64 encoded text file:
> /usr/bin/base64 < test.jpg > test.64

If you must to use the pg shell, perhaps coding Misa's function in other language (python f.ex.) allows you directly insert the bytea.

A use hint: disable toast compression for that table, images are already compressed, you don't need to waste time with it.

> That outputs a base64 string that matches test.64. Outputting that to a
> file and then converting it back gives me my image:
> /usr/bin/base64 -d < output.64 > newtest.jpg
>
> Like I said, kind of crazy, but it satisfies me that my basic premise is
> doable. I'll still get one of the front-end developers to whip out some PHP
> just to be safe.
>
> Thanks to all!

--- ---
Eduardo Morras <emorrasg(at)yahoo(dot)es>

--
Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Thomas Kellerer 2013-05-10 08:11:35 Re: Storing small image files
Previous Message Vegard Bønes 2013-05-10 07:33:14 Large amount of serialization errors in transactions