Re: [PERFORM] Sort-of replication for reporting purposes

2017-01-13 Thread Phillip Couto
-performance@postgresql.orgSubject: Re: [PERFORM] Sort-of replication for reporting purposes On 13 January 2017 at 12:00, Stuart Bishop <stu...@stuartbishop.net> wrote:On 7 January 2017 at 02:33, Ivan Voras <ivo...@gmail.com> wrote: I forgot to add one more information, the databases are 50G+ e

Re: [PERFORM] Sort-of replication for reporting purposes

2017-01-13 Thread Stuart Bishop
On 13 January 2017 at 18:17, Ivan Voras wrote: > On 13 January 2017 at 12:00, Stuart Bishop > wrote: > >> >> >> On 7 January 2017 at 02:33, Ivan Voras wrote: >> >>> >>> >>> >>> I forgot to add one more information, the databases are 50G+ each so >>> doing the base backup on demand over the netw

Re: [PERFORM] Sort-of replication for reporting purposes

2017-01-13 Thread Ivan Voras
On 13 January 2017 at 12:00, Stuart Bishop wrote: > > > On 7 January 2017 at 02:33, Ivan Voras wrote: > >> >> >> >> I forgot to add one more information, the databases are 50G+ each so >> doing the base backup on demand over the network is not a great option. >> > > If you don't want to rebuild

Re: [PERFORM] Sort-of replication for reporting purposes

2017-01-13 Thread Stuart Bishop
On 7 January 2017 at 02:33, Ivan Voras wrote: > > > On 6 Jan 2017 8:30 p.m., "Scott Marlowe" wrote: > > On Fri, Jan 6, 2017 at 12:24 PM, Ivan Voras wrote: > > Hello, > > > > I'm investigating options for an environment which has about a dozen > servers > > and several dozen databases on each, a

Re: [PERFORM] Sort-of replication for reporting purposes

2017-01-12 Thread ProPAAS DBA
On 01/06/2017 12:24 PM, Ivan Voras wrote: Hello, I'm investigating options for an environment which has about a dozen servers and several dozen databases on each, and they occasionally need to run huge reports which slow down other services. This is of course "legacy code". After some discu

Re: [PERFORM] Sort-of replication for reporting purposes

2017-01-06 Thread Stephen Frost
Ivan, * Ivan Voras (ivo...@gmail.com) wrote: > I'm investigating options for an environment which has about a dozen > servers and several dozen databases on each, and they occasionally need to > run huge reports which slow down other services. This is of course "legacy > code". After some discussi

Re: [PERFORM] Sort-of replication for reporting purposes

2017-01-06 Thread Rick Otten
I suggest SymmetricDS. ( http://symmetricds.org ) I've had good luck using them to aggregate data from a heterogeneous suite of database systems and versions back to a single back-end data mart for exactly this purpose. On Fri, Jan 6, 2017 at 2:24 PM, Ivan Voras wrote: > Hello, > > I'm inves

Re: [PERFORM] Sort-of replication for reporting purposes

2017-01-06 Thread Ivan Voras
On 6 Jan 2017 8:30 p.m., "Scott Marlowe" wrote: On Fri, Jan 6, 2017 at 12:24 PM, Ivan Voras wrote: > Hello, > > I'm investigating options for an environment which has about a dozen servers > and several dozen databases on each, and they occasionally need to run huge > reports which slow down oth

Re: [PERFORM] Sort-of replication for reporting purposes

2017-01-06 Thread Scott Marlowe
On Fri, Jan 6, 2017 at 12:24 PM, Ivan Voras wrote: > Hello, > > I'm investigating options for an environment which has about a dozen servers > and several dozen databases on each, and they occasionally need to run huge > reports which slow down other services. This is of course "legacy code". > Af

[PERFORM] Sort-of replication for reporting purposes

2017-01-06 Thread Ivan Voras
Hello, I'm investigating options for an environment which has about a dozen servers and several dozen databases on each, and they occasionally need to run huge reports which slow down other services. This is of course "legacy code". After some discussion, the idea is to offload these reports to se