To increase performance, I'm thinking about storing copies of less frequently changed tables in a client computer. At startup client application compares last change times and downloads newer tables from server. CREATE TABLE lastchange ( tablename CHAR(8) PRIMARY KEY, lastchange timestamp without time zone ); INSERT INTO lastupdated (tablename) values ('mytable1'); .... INSERT INTO lastupdated (tablename) values ('mytablen'); CREATE OR REPLACE FUNCTION setlastchange() RETURNS "trigger" AS $$BEGIN UPDATE lastchange SET lastchange='now' WHERE tablename=TG_RELNAME; RETURN NULL; END$$ LANGUAGE plpgsql STRICT; CREATE TRIGGER mytable1_trig BEFORE INSERT OR UPDATE OR DELETE ON mytable1 EXECUTE PROCEDURE setlastchange(); .... CREATE TRIGGER mytablen_trig BEFORE INSERT OR UPDATE OR DELETE ON mytablen EXECUTE PROCEDURE setlastchange(); Is table caching good idea? Is this best way to implement table caching ? Andrus. ---------------------------(end of broadcast)--------------------------- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to majordomo@xxxxxxxxxxxxxx so that your message can get through to the mailing list cleanly