Peter,
I have just finished up some other stuff in the backend, and I was
wondering what to do next. My personal list include a cleanup of the lo
type. Specifically:
1. Assign a fixed OID to the LO type so that attributes of this type
can easily be identified.
2. Write a VACUUM LO procedure.
3. Extend/verify the existing internal lo functions to work with the
new type.
I know that more can/should be done in this area, but I only have so much
time. I am aware the you have done some work on this in the contrib area.
Were you planning on handling any (or all) of these issues as part of the
6.4 base release? I will gladly move on to something else.
Peter T Mount wrote:
> On Wed, 5 Aug 1998, Sergey E. Levov wrote:
>
> > Hello!
> >
> > I've written the SPI procedure which allows to delete large
> > objects referenced by currently deleted or updated tuples.
> > I tested it with PostgreSQL v6.3.2 and seem it works.
> > If PostgreSQL developers team is interested in it, I'll send
> > the sources to this mailing list or to somebody personally.
>
> I'll be interested (I wrote the copy in contrib/lo - post 6.3.2 source
> tree).
>
> There was some talk about 5 weeks ago about using vacuum to pick up any
> stragglers. I have some ideas on this, but can't try them out at the
> moment - I haven't had a working backend for about 3 weeks now :-(
