Automatic on-line replication
От
Gordan Bobic
Тема
Automatic on-line replication
Дата
Msg-id
000b01c07632$55bf0bc0$8000000a@localdomain
Список
Дерево обсуждения
Re: Outer Joins "Poul L. Christiansen" <poulc@cs.auc.dk>
Re: Outer Joins "Robert B. Easter" <reaster@comptechnews.com>
Re: Outer Joins Tom Lane <tgl@sss.pgh.pa.us>
Re: Outer Joins "Robert B. Easter" <reaster@comptechnews.com>
Re: Outer Joins "Robert B. Easter" <reaster@comptechnews.com>
Re: Outer Joins Tom Lane <tgl@sss.pgh.pa.us>
Re: Outer Joins "Robert B. Easter" <reaster@comptechnews.com>
Re: Outer Joins Tom Lane <tgl@sss.pgh.pa.us>
Re: Outer Joins Bruce Momjian <pgman@candle.pha.pa.us>
Re: Outer Joins "Robert B. Easter" <reaster@comptechnews.com>
Re: Outer Joins Tom Lane <tgl@sss.pgh.pa.us>
Re: Outer Joins Bruce Momjian <pgman@candle.pha.pa.us>
Re: Outer Joins Tom Lane <tgl@sss.pgh.pa.us>
JRelationalFramework Erik Tennant <lists@webpd.com>
Re: Outer Joins "Brett W. McCoy" <bmccoy@chapelperilous.net>
Does postgres include this feature? Can someone point me toward the docs? This is regarding the old clustering thread. If the on-line replication is implemented, then it could be used for a form of clustering, because the SELECTs could be distributed across multiple servers (one on each server). Obviously, this would require the complete database to be on each server, but until more advanced clustering methods are implemented, I don't see another sensible way of doing clustering for situations where one server just cannot feasibly cut it. Besides, insuring completeness of the returned results when doing a multi-table join across multiple servers is a mind numbingly hard problem... I am also guessing that record locking would not work properly if multiple computers were accessing the same physical database file that is mounted on a remote file system. Is this the case? Not that I am even thinking about trying to access data files via NFS or DFS... ;-) Regards. Gordan
В списке pgsql-general по дате отправления