I should have been clearer - this difference occurs immediately after a
one-time-copy from the existing db server to an essentially 'blank'
receiving db server. both machines are same architecture, disks, etc etc
(AWS).
On 7/25/2013 07:58, Greg Sabino Mullane wrote:
On Tue, Jul 23, 2013 at 02:49:21PM -0700, Paul Theodoropoulos wrote:
...
measure of a database's consistency - that much I do realize. So
this could just be a byproduct of trigger-based transfer of data to
a blank db - I dunno (obligatory /not a pgdba from me). I ran a
'vacuum full' but there was no change in space consumed.
I would try doing a pg_relation_size() and pg_total_replication_size() on
the exact tables in question - it could simply be that the slave has
non-replicated items in its database that the master does not.
--
Paul Theodoropoulos
www.anastrophe.com
_______________________________________________
Bucardo-general mailing list
[email protected]
https://mail.endcrypt.com/mailman/listinfo/bucardo-general
