From: | "Paolo Bizzarri" <pibizza(at)gmail(dot)com> |
---|---|
To: | "Richard Huxton" <dev(at)archonet(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Corruption of files in PostgreSQL |
Date: | 2007-05-30 09:43:03 |
Message-ID: | 5213d1d20705300243u54c644bm243893052ae51d82@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 5/30/07, Richard Huxton <dev(at)archonet(dot)com> wrote:
> Paolo Bizzarri wrote:
> > We use postgres as a backend, and we are experimenting some corruption
> > problems on openoffice files.
>
> 1. How are you storing these files?
Files are stored as large objects. They are written with an lo_write
and its contents is passed as a Binary object.
> 2. What is the nature of the corruption?
Apparently, files get truncated.
> > As our application is rather complex (it includes Zope as an
> > application server, OpenOffice as a document server and as a client)
> > we need some info on how to check that we are interacting correctly
> > with Postgres.
>
> Shouldn't matter.
I hope so...
> > We are currently using:
> >
> > - PostgreSQL 7.4.8;
>
> Well, you need to upgrade this - version 7.4.17 is the latest in the 7.4
> series. You are missing 9 separate batches of bug and security fixes.
Ok. We will upgrade and see if this can help solve the problem.
>
> > - pyscopg 1.1.11;
> > - Zope 2.7.x;
> > - Openoffice 2.2.
>
> None of this should matter really, unless there's some subtle bug in
> psycopg causing corruption of data in-transit.
>
> Let's get some details on the two questions above and see if there's a
> pattern to your problems.
Ok. Thank you.
Paolo Bizzarri
Icube S.r.l.
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Huxton | 2007-05-30 09:56:11 | Re: Corruption of files in PostgreSQL |
Previous Message | Richard Huxton | 2007-05-30 09:30:16 | Re: Corruption of files in PostgreSQL |