From: | Rick Otten <rottenwindfish(at)gmail(dot)com> |
---|---|
To: | Ivan Voras <ivoras(at)gmail(dot)com> |
Cc: | postgres performance list <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Sort-of replication for reporting purposes |
Date: | 2017-01-06 19:33:04 |
Message-ID: | CAMAYy4Jmu1jpRhUvxdfJExXkCECYZMG5vZo9A8dQw3Y1dcDqCg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
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 <ivoras(at)gmail(dot)com> 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 discussion, the idea is to offload these reports to
> separate servers - and that would be fairly straightforward if not for the
> fact that the report code creates temp tables which are not allowed on
> read-only hot standby replicas.
>
> So, the next best thing would be to fiddle with the storage system and
> make lightweight snapshots of live database clusters (their storage
> volumes) and mount them on the reporting servers when needed for the
> reports. This is a bit messy :-)
>
> I'm basically fishing for ideas. Are there any other options available
> which would offer fast replication-like behaviour ?
>
> If not, what practices would minimise problems with the storage snapshots
> idea? Any filesystem options?
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2017-01-06 19:43:03 | Re: Sort-of replication for reporting purposes |
Previous Message | Ivan Voras | 2017-01-06 19:33:00 | Re: Sort-of replication for reporting purposes |