|
Home > Archive > PostgreSQL SQL > November 2005 > Re: idea for a geographically distributed database: how best
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Re: idea for a geographically distributed database: how best
|
|
| Achilleus Mantzios 2005-11-17, 11:23 am |
| O codeWarrior έγραψε στις Nov 17, 2005 :
> Sounds like a mis-guided approach to me...
>
> You might want to consider using latitude and longitude or zip codes or
> taking more of a traditional "GIS" approach rather than duplicating data
> across redundant databases.
>
> Another issue is that you end up having to query every database to find
> proximity... Suppose you have 500 "cells" ? You now have to invoke some sort
> of RPC mechanism on 499 other RDBMS, manage 500 user names and passwords,
> retrieve potentially 500 recordsets, merge the data, etc...
>
> Your problems will continue to get more and more complex... You are better
> off with a single RDBMS and a single schema...
Andy, i agree with what codeWarrior says.
But if you are interested in replication, dbmirror is very elegant
(altho not as trendy) simple, and highly customizable replication
solution.
I have heavily modified dbmirror to even support
Asynchronous Conditional row grained
Foreign key dependency Traversal oriented
Lazy Replication!!!
(which ofcourse nobody wants :)
>
>
>
>
> "Andy Ballingall" <andy@areyoulocal.co.uk> wrote in message
> news:ECOWS04Mp8nkfZy
ufzT00010fe4@smtp-out4.blueyonder.co.uk...
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
> choose an index scan if your joining column's datatypes do not
> match
>
--
-Achilleus
---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
| |
| Andy Ballingall 2005-11-17, 11:23 am |
|
>Andy, i agree with what codeWarrior says.
But if you are interested in replication, dbmirror is very elegant
(altho not as trendy) simple, and highly customizable replication
solution.
I have heavily modified dbmirror to even support
Asynchronous Conditional row grained
Foreign key dependency Traversal oriented
Lazy Replication!!!
(which ofcourse nobody wants :)
I'll go and check it out, so even if I don't want to use it, I'll at least
know what it means!
(I considered suggesting using an acronym for it, but 'ACRGFKDTOLR' made my
lips bleed when I tried to say it).
Thanks,
Andy
>
>
>
>
> "Andy Ballingall" <andy@areyoulocal.co.uk> wrote in message
> news:ECOWS04Mp8nkfZy
ufzT00010fe4@smtp-out4.blueyonder.co.uk...
mind[color=darkred]
it.[color=darkred]
cell[color=darkred]
up[color=darkred]
by[color=darkred]
server.[color=darkred]
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
> choose an index scan if your joining column's datatypes do not
> match
>
--
-Achilleus
---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.362 / Virus Database: 267.13.3/173 - Release Date: 16/11/2005
---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster
|
|
|
|
|