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?
On 1/12/16 6:02 AM, Pedro França wrote:
> 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.
You should consider using the Postgres FDW
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.
I'm evaluating the use of PostgreSQL to our production mission-critical
application that currently runs on SQL Server 2012.
There is a huge partitioned table of archived information that is
occasionally queried (+5TB) and are not required to be 24/7 online. An
eventual failure on the filesystem
