From: | Richard Huxton <dev(at)archonet(dot)com> |
---|---|
To: | Frank Hagstrom <frank(dot)hagstrom(at)gmail(dot)com> |
Cc: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: Possible to use a table to tell what table to select from? |
Date: | 2005-07-14 08:31:01 |
Message-ID: | 42D622C5.9000907@archonet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
Frank Hagstrom wrote:
> Hello
>
> I've been thinking on a potential problem I might get in a distant
> future, but once I started thinking on it I just as well had to
> check...
>
> Is it possible to have say ~ 6 tables, where the first one is a
> 'reference' to all the others (they all are with the same structure).
> The other 5 or so have information stored in importance/access/age,
> where one table will be only recent/important things, the other with a
> bit lower priority and so on until the last table that can be really
> huge and slow and used more like a storage ... Is it possible to write
> an SQL query to let the first table figure out what table one will do
> the actual select from?
If the tables are all holding the same sort of thing, e.g. logs2003,
logs2004, logs2005 etc. then you might want to look at partitioning.
This is being looked at for the next version, check the archives of the
hackers list.
--
Richard Huxton
Archonet Ltd
From | Date | Subject | |
---|---|---|---|
Next Message | Vivek | 2005-07-14 09:24:17 | Yearly Archival System Using PostgreSQL |
Previous Message | Richard Huxton | 2005-07-14 08:14:15 | Re: function parameters : bug? |