Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.4) with ESMTP id f9HFYQP50979 for ; Wed, 17 Oct 2001 11:34:26 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id f9HFYLc27138; Wed, 17 Oct 2001 11:34:21 -0400 (EDT) To: Reiner Dassing cc: pgsql-sql@postgresql.org Subject: Re: Triggers do not fire In-reply-to: <3BCDA3E1.96B027EA@wettzell.ifag.de> References: <3BCC2CBB.9C3A31EF@wettzell.ifag.de> <22705.1003268168@sss.pgh.pa.us> <3BCDA3E1.96B027EA@wettzell.ifag.de> Comments: In-reply-to Reiner Dassing message dated "Wed, 17 Oct 2001 17:29:37 +0200" Date: Wed, 17 Oct 2001 11:34:21 -0400 Message-ID: <27135.1003332861@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200110/241 X-Sequence-Number: 5196 Reiner Dassing writes: > I have a table which has a lot of entries (some x millions) of the kind > (id, timestamp, value) > The access (selects) is concentrated to the timely last some thousands > entries. > To adapt this fact I want to setup a "virtual" table - test in my > example - which > is accessed by the clients but in reality the entries are separated to > different small > tables. These table are dynamically created to hold the values > distinguished by years. Why bother? Seems like you are just making life complicated for yourself. One big table with a suitable index ought to work fine. regards, tom lane