Re: [HACKERS] Deleting loid from the database
contrib/vacuumlo perhaps? Michael Fuhr wrote: On Sat, Mar 04, 2006 at 12:08:52PM +0530, Md.Abdul Aziz wrote: I am a presently working on a module which enhances postgre to store audio files,while storing the aduido file in the databese i used liod,now the problem is i am able to unlink but still the data is present in the postgre database.can some one suggest me how to delete (not unlink) large objects from the postgre databse. VACUUM FULL pg_largeobject might be what you're looking for, but if you're going to reload the data then an ordinary VACUUM (without FULL) will free the space for re-use by PostgreSQL without shrinking the file (unless the table has no live tuples, in which case the file size will be zeroed). ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [HACKERS] Deleting loid from the database
On Sun, Mar 05, 2006 at 09:54:02PM +0800, Christopher Kings-Lynne wrote: contrib/vacuumlo perhaps? vacuumlo only calls lo_unlink(); the data still exists in pg_largeobject due to MVCC. -- Michael Fuhr ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[HACKERS] Deleting loid from the database
Hi, I am a presently working on a module which enhances postgre to store audio files,while storing the aduido file in the databese i used liod,now the problem is i am able to unlink but still the data is present in the postgre database.can some one suggest me how to delete (not unlink) large objects from the postgre databse. Thanking you, Md.Abdul Aziz ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [HACKERS] Deleting loid from the database
On Sat, Mar 04, 2006 at 12:08:52PM +0530, Md.Abdul Aziz wrote: I am a presently working on a module which enhances postgre to store audio files,while storing the aduido file in the databese i used liod,now the problem is i am able to unlink but still the data is present in the postgre database.can some one suggest me how to delete (not unlink) large objects from the postgre databse. VACUUM FULL pg_largeobject might be what you're looking for, but if you're going to reload the data then an ordinary VACUUM (without FULL) will free the space for re-use by PostgreSQL without shrinking the file (unless the table has no live tuples, in which case the file size will be zeroed). -- Michael Fuhr ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
