On 1 December 2011 03:44, Craig Ringer <ring...@ringerc.id.au> wrote: > Streaming replication works on a rather lower level than that. It records > information about transaction starts, rollbacks and commits, and records > disk block changes. It does not record SQL statements. It's not using > INSERT, so you can't switch to COPY. Streaming replication basically just > copies the WAL data, and WAL data is not all that compact.
My thought was about saving bytes on the information about transaction starts, rollbacks and commits. I case of lost of small inserts each in different transaction I suppose there will be more data like this. > Try to run streaming replication over a compressed channel. PostgreSQL might > gain the ability to do this natively - if someone cares enough to implement > it and if it doesn't already do it without my noticing - but in the mean > time you can use a compressed SSH tunnel, compressed VPN, etc. Thank you for the advice. > Alternately, investigate 3rd party replication options like Slony and > Bucardo that might be better suited to your use case. > > -- > Craig Ringer -- Sergey Konoplev Blog: http://gray-hemp.blogspot.com LinkedIn: http://ru.linkedin.com/in/grayhemp JID/GTalk: gray...@gmail.com Skype: gray-hemp -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
