pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Reiner Dassing <dassing@wettzell.ifag.de>
Cc: pgsql-sql@postgresql.org
Subject: Re: Triggers do not fire
Date: Wed, 17 Oct 2001 11:34:21 -0400
Message-ID: <27135.1003332861@sss.pgh.pa.us> (raw)
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>

Reiner Dassing <dassing@wettzell.ifag.de> 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



view thread (7+ messages)  latest in thread

Message-ID: <27135.1003332861@sss.pgh.pa.us>
Permalink:  ../27135.1003332861@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/27135.1003332861@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: tgl@sss.pgh.pa.us, dassing@wettzell.ifag.de
  Subject: Re: Triggers do not fire
  In-Reply-To: <27135.1003332861@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox