If you setup rules on the view and just have the application select, insert, update, and delete from the view instead of the raw tables you won't need to change your application at all. Though you do need to be aware that you can't easily enforce uniqueness across multiple tables. As for clearing the fields, if by clearing you mean setting to NULL then you're correct, it would save space. Just remember that you won't actually be able to use the saved space until the table is vacuumed. On Fri, Apr 15, 2005 at 04:22:07PM +0200, Enrico Weigelt wrote: > > Hi folks, > > > we've got an quite large table with 17 columns and now >15k rows. > The table works also as an journal will continously grow day by day. > Man of the columns (mostly text) aren't needed anymore if the tuple > has reached a certain age. > So I thought about clearing the unnecessary fields of old tuples > to save resources. Does it bring any performance improvement ? > > Of I could splitt off this table an working- an archive- table > and map them together in some views - someday I probably *will* > do it - but our applications are not yet ready for this. > > > thx > -- > --------------------------------------------------------------------- > Enrico Weigelt == metux IT service > > phone: +49 36207 519931 www: http://www.metux.de/ > fax: +49 36207 519932 email: contact@xxxxxxxx > cellphone: +49 174 7066481 > --------------------------------------------------------------------- > -- DSL ab 0 Euro. -- statische IP -- UUCP -- Hosting -- Webshops -- > --------------------------------------------------------------------- > > ---------------------------(end of broadcast)--------------------------- > TIP 4: Don't 'kill -9' the postmaster > -- Jim C. Nasby, Database Consultant decibel@xxxxxxxxxxx Give your computer some brain candy! www.distributed.net Team #1828 Windows: "Where do you want to go today?" Linux: "Where do you want to go tomorrow?" FreeBSD: "Are you guys coming, or what?"
