| From: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
|---|---|
| To: | Poul Jensen <flyvholm(at)gfy(dot)ku(dot)dk> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: SQL - planet redundant data |
| Date: | 2005-09-09 23:50:51 |
| Message-ID: | 20050909235051.GQ7630@pervasive.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Sep 08, 2005 at 07:58:55PM -0800, Poul Jensen wrote:
> This novice must be missing a sneaky way to avoid massive redundancy and
> still maintain easy access. I've been suggested to look at inheritance
> and foreign keys. Foreign keys I don't see how to use, but I could make
What you seem to be looking for is a form of partitioning. PostgreSQL
doesn't currently support partitioning of this form, but there's work in
progress to change that.
As someone else mentioned, you could do it with a union all view.
http://cvs.distributed.net/viewcvs.cgi/stats-sql/logdb/ has an example
of this.
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim C. Nasby | 2005-09-09 23:54:16 | Re: RAID0 and pg_xlog |
| Previous Message | Jim C. Nasby | 2005-09-09 23:42:10 | Re: Support for Limit in Update, Insert... |