Bug #601: libpq needs a lo_truncate() or INV_TRUNC - Mailing list pgsql-bugs

From pgsql-bugs@postgresql.org
Subject Bug #601: libpq needs a lo_truncate() or INV_TRUNC
Date
Msg-id 20020222230756.CD6DA475D75@postgresql.org
Whole thread Raw
List pgsql-bugs
Aaron Hillegass (aaron@bignerdranch.com) reports a bug with a severity of 2
The lower the number the more severe it is.

Short Description
libpq needs a lo_truncate() or INV_TRUNC

Long Description
I'm using the large object interface to store documents.  Sometimes the documents are edited and get larger (take up
morememory).  This is fine,  I just lo_write out the new version of the document.  Other times,  the documents get
editedand get smaller.  This is bad because I can't find any way to make the large object smaller.  
 

Following unix conventions,  it would be nice to have a lo_truncate() to make the large object a specific length.  Or,
aflag to lo_open() that would make the opened large object zero-length (INV_TRUNC seems like a natural name for the
flag).

Sample Code


No file was uploaded with this report

pgsql-bugs by date:

Previous
From: Coax
Date:
Subject: Possible bug concerning LASTOID in 7.2
Next
From: Tom Lane
Date:
Subject: Re: CURRENT_TIMESTAMP not work correctly insinde a transaction.