Restore dump are real data with transformers about replibyte HOT 3 OPEN

I have the same issue. Seemingly correctly configured .yml file outputs exactly the same data. No transformation takes place.

I am running the following commands, to no avail:
cat test_dump.sql | replibyte -c conf.yml dump create -i -s postgresql
replibyte -c conf.yml dump restore local -i postgres -v latest -o > test_transform.sql

Can anyone shed any light on this?

from replibyte.

Same issue here, I took a local dump, transformed it, then restored it back.Does transformation not work on existing dumps? Makes this useless as I need to use already existing dumps.

from replibyte.

Actually got this to work. It seems that I had to use the command below to get a dump. Its the dump format ... if it uses sql statements (i.e. insert) then it should transform the data. But if it uses COPY public.table (column_a, colum_b) FROM stdin; then data is NOT transformed.

pg_dump --column-inserts --no-owner -p 5434 -U postgres postgres

It would be nice if replibyte could support this more compressed dump format.

from replibyte.