| From: | "Nigel J(dot) Andrews" <nandrews(at)investsystems(dot)co(dot)uk> |
|---|---|
| To: | Cornelia Boenigk <poppcorn(at)cornelia-boenigk(dot)de> |
| Cc: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Rens Admiraal <postgresnews(at)etraned(dot)nl>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: BLOB problem |
| Date: | 2004-02-04 07:23:29 |
| Message-ID: | Pine.LNX.4.21.0402040719000.10497-100000@ponder.fairway2k.co.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, 4 Feb 2004, Cornelia Boenigk wrote:
> Hello
>
> > I've encountered a problem with a PostgreSQL database
>
> Are you sure that the problem is with PostgreSQL?
>
> I was testing pg_lo_import() with PHP 4.3.x and found it buggy. I had
> the opposite problem: only a few bytes from a large object were stored
> in the database. Then I downgraded to PHP 4.2 and the same script
> works well on the same database.
I never had any problems with LOs on a php 4.3.x <--> Postrgresql system I was
working on last year. There must have been something else happening that isn't
attributable to use of LOs.
--
Nigel J. Andrews
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lincoln Yeoh | 2004-02-04 07:50:22 | Re: postmaster growing to consume all memory |
| Previous Message | Christopher Kings-Lynne | 2004-02-04 07:10:14 | Re: pg_generate_sequence and info_schema patch (Was: SELECT |