From: | Frank Hagstrom <frank(dot)hagstrom(at)gmail(dot)com> |
---|---|
To: | Richard Huxton <dev(at)archonet(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 15:26:09 |
Message-ID: | 28b4448e0507140826617e9c2a@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
On 7/14/05, Richard Huxton <dev(at)archonet(dot)com> wrote:
> 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
>
Ah ok, thanks I'll look into the partitioning then :)
(not really logs, but will work in the same way, as I'm planning to
use it to hold revisions, but it will have the same format in the
tables...)
/Frank H
From | Date | Subject | |
---|---|---|---|
Next Message | marco_0160 | 2005-07-14 15:48:36 | [postgres] Betrifft: Datumsfeld leer lassen |
Previous Message | Dhanashree | 2005-07-14 14:23:04 | difference between all RDBMSs |