Thank you for your response David.
Yea, we are considering doing all the function calls and access to tables with dblink and see how bad this would hurt performance. It will be tough to explain this to the SQL Server guys.
Maybe there is another approach to deal with this kind of environment? Does Postgres only relies on replication for high availability? Maybe an extension that I don't know about?
Any help is appreciated.
Thank you
2016-01-11 22:11 GMT-02:00 David Steele <david@xxxxxxxxxxxxx>:
On 1/11/16 8:41 AM, Pedro França wrote:
I've tried to put the data on another database but it didn't help as
tablespaces are required cluster-wide on startup.
If putting the data in a separate database works for you then it wouldn't be a big leap to put it in a separate cluster. Functionality-wise it's pretty similar since you can't join across databases in Postgres.
There are some advantages to this design since you can separate the buffer caches, tune optimizer variables, wal settings, etc.
--
-David
david@xxxxxxxxxxxxx
PEDRO IVO | Administrador de Banco de Dados GolSat | Líder em Sustentabilidade
pedro.franca@xxxxxxxxxxxxx | (43) 3315.9545 | www.golsat.com.br
