From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> |
Cc: | pgsql-www(at)postgresql(dot)org, Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, Greg Sabino Mullane <greg(at)turnstep(dot)com> |
Subject: | Re: Yet another infrastructure problem |
Date: | 2008-10-25 20:49:59 |
Message-ID: | 49038677.3050603@hagander.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-www |
Robert Treat wrote:
> On Saturday 25 October 2008 04:23:34 Magnus Hagander wrote:
>> The login system would also be good to have distributed, but it's used
>> by orders of magnitude less number of people. But if we replicate the
>> database off to the other machine, it should be possible to point the
>> logins on both machines as well - it's a simple pl/pgsql function that
>> needs to be called. We'll just need to deal with the "last logged in"
>> part that won't work then.
>>
>
> If you used plproxy rather plpgsql, i think you could eliminate this problem.
>
Does pl/proxy actually help with that? I haven't actually used it, but
from what I can tell dealing with failover is still on the TODO list for
it ("RUN ON ANY: if one con failed, try another"). Or?
//Magnus
From | Date | Subject | |
---|---|---|---|
Next Message | Russell Smith | 2008-10-26 01:03:43 | Re: Yet another infrastructure problem |
Previous Message | Koen Martens | 2008-10-25 19:01:48 | Re: hosting postgresql.{nl,be} |