On 10/05/2015 09:46 AM, jimbosworth wrote:
Im not in a position to change the database setup on server A.
Can you have the owners/maintainers do the needed changes to setup
replication?
Or that is 100% out of the question?
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org
Thanks Bill, but is there no way to just track row changes on a postgres
table without using 3rd party replication solutions or a patched version of
postgres?
Im not in a position to change the database setup on server A. Server B is
mine to maintain, hence why postgres_fdw and some means of trac
On Mon, 5 Oct 2015 06:20:28 -0700 (MST)
jimbosworth wrote:
> Hi All,
>
> I have two servers each running pg9.4.4 database instances.
> I need to determine the best way to keep a large 20gb table on server A
> synchronised onto server B...
>
> At the moment, I use pg_dump to periodically dump
Hi All,
I have two servers each running pg9.4.4 database instances.
I need to determine the best way to keep a large 20gb table on server A
synchronised onto server B...
At the moment, I use pg_dump to periodically dump the table on server A,
then psql to reload into server B. This is fine, bu
