| From: | "Alexander Staubo" <alex(at)purefiction(dot)net> |
|---|---|
| To: | "Jeff Davis" <pgsql(at)j-davis(dot)com> |
| Cc: | "Gregory Stark" <stark(at)enterprisedb(dot)com>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, gonzales(at)linuxlouis(dot)net, "Guillaume Lelarge" <guillaume(at)lelarge(dot)info>, "Kenneth Downs" <ken(at)secdat(dot)com>, nikolay(at)samokhvalov(dot)com, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Slightly OT. |
| Date: | 2007-06-01 23:44:51 |
| Message-ID: | 88daf38c0706011644o1852e0bdqa0fdc4072508abfa@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 6/2/07, Jeff Davis <pgsql(at)j-davis(dot)com> wrote:
> Here is some work going on that looks like what you want:
>
> http://archives.postgresql.org/pgsql-hackers/2007-03/msg00050.php
I had no idea someone was working on WAL-log-based replication; I saw
the TODO entry a while ago, but I missed the thread. I think WAL
replication is a beautiful idea, so I'll gladly throw my support
behind this. Thanks for the pointer.
> You might also seriously consider PgPool-II.
pgpool-II seems like a decent idea. I'm not sure if the partitioning
can support referential integrity though -- would they have to be
declared as CHECK constraints that used dblink()?
Also, it doesn't seem capable of planning a query intelligently, which
means that a query such as "select * from foo where id = 123" is going
to be aggregated across all nodes even though only one node has the
partition covering the id range [0, 1000], say.
Alexander.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron Johnson | 2007-06-01 23:52:02 | Re: One last Slony question (was Re: Slightly OT.) |
| Previous Message | Joshua D. Drake | 2007-06-01 23:35:27 | Re: One last Slony question (was Re: Slightly OT.) |