From: | Tom Lane <tgl> |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql/src/backend/storage/large_object (inv_api.c) |
Date: | 2000-06-15 06:07:34 |
Message-ID: | 200006150607.e5F67Yl07743@hub.org |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Date: Thursday, June 15, 2000 @ 02:07:34
Author: tgl
Update of /home/projects/pgsql/cvsroot/pgsql/src/backend/storage/large_object
from hub.org:/home/projects/pgsql/tmp/cvs-serv7669
Modified Files:
inv_api.c
----------------------------- Log Message -----------------------------
Repair Large Object bugs demonstrated by Ian Grant's example. inv_write
was inappropriately relying on rel->rd_nblocks to tell if the LO is
empty (apparently a hack to get around a long-dead index bug), causing
misbehavior on a written-but-never-vacuumed LO. Also, inv_read failed
to cope gracefully with 'holes' (unwritten regions) in the object.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2000-06-15 06:10:28 | REL7_0_PATCHES pgsql/src/backend/storage/large_object (inv_api.c) |
Previous Message | Bruce Momjian - CVS | 2000-06-15 04:12:47 | REL7_0_PATCHES pgsql/src/interfaces/jdbc/org/postgresql/jdbc2 (Connection.java ResultSet.java Statement.java) |