| From: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
|---|---|
| To: | cq(at)htec(dot)demon(dot)co(dot)uk |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Postgres Problemo... |
| Date: | 2000-05-19 12:47:46 |
| Message-ID: | 20000519214746P.t-ishii@sra.co.jp |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Hi Tatsuo,
>
> Sorry to bother you but I noticed in the HISTORY file of Postgres-7.0
> this entry relating to 6.5.2:
>
> Fix for large object write-in-middle, no extra block, memory consumption(Tatsuo)
>
> I am using 6.5.2 (7.0 proved too buggy)
What kind of bugs have you found with 7.0?
> but I am getting this problem with
> the Large Object interface:
>
> I lo_lseek to a middle position, lo_read a header of my record,
> lo_read the rest according to size in header, lo_lseek to previous position,
> then lo_write an altered record: any position not written to in the LO
> at the time is trashed and bears no resemblance to previous content.
> As if the Lob FD no longer referred to the right object just garbage.
> I think it is the combination of calls prior to the write, because I
> do single seek/writes elsewhere in my app no problem.
>
>
> I am wondering whether this is the problem you fixed and which version
> the fix actually went into!?
>
> yours sincerely,
> Chris Quinn
Ok, give me some time to dig into problems you mentioned.
(I'm very busy this month).
--
Tatsuo Ishii
| From | Date | Subject | |
|---|---|---|---|
| Next Message | The Hermit Hacker | 2000-05-19 12:48:02 | Re: Re: Heaps of read() syscalls by the postmaster |
| Previous Message | The Hermit Hacker | 2000-05-19 12:42:30 | Re: Performance (was: The New Slashdot Setup (includes MySql server)) |