From: | "Michael Nolan" <htfoot(at)gmail(dot)com> |
---|---|
To: | "Paolo Bizzarri" <pibizza(at)gmail(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Corruption of files in PostgreSQL |
Date: | 2007-06-02 20:24:04 |
Message-ID: | 4abad0eb0706021324g71f5c956i5b940018885357c3@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 6/2/07, Paolo Bizzarri <pibizza(at)gmail(dot)com> wrote:
>
>
> What we are trying to understand is, first and foremost, if there are
> known cases under which PostgreSQL can truncate a file.
I think it's somewhat more likely that whatever is sending the file to PG is
the cause, either in how it handles the file or due to communications
issues.
This sounds similar to a problem I experienced with an application I wrote
that takes files extracted from email (using MHonarc) and stores them in a
PG database so that I can render them using a web browser later on. I wound
up having to store the files in BASE64 encoding to keep them from getting
corrupted.
--
Mike Nolan
From | Date | Subject | |
---|---|---|---|
Next Message | Harpreet Dhaliwal | 2007-06-02 20:51:13 | Re: Transactional DDL |
Previous Message | Leif B. Kristensen | 2007-06-02 19:52:13 | Re: Transactional DDL |