Greenmask V0.1.13 SIGSEGV about greenmask

[wwoytenko]

Hi! Thank you for reporting!

github.com/greenmaskio/greenmask/internal/db/postgres/dumpers.(*BlobsDumper).Execute.func2.2()

Looks like the seg fault is in Large Object dumping. I will check this tomorrow. There is definitely a bug.

On a different note, I've also found that greenmask dump --data-only gives a schema collision error : "pg_dump: error: options -s/--schema-only and -a/--data-only cannot be used together"

Well, you're right. I will review this case tomorrow as well.

[wwoytenko]

I've created #103 PR, but I will review the logic. I think there might be high resource utilization without a worker pool pattern. I will keep you posted

[TCY16]

Thanks for the super quick turnaround! I'll post more issues if they come up 😄

[wwoytenko]

@TCY16

The large object dumper seg fault I hope will be fixed in #103

The fix is expected to be published as v0.1.14 on Thursday (09.05.2024)

Regarding this

On a different note, I've also found that greenmask dump --data-only gives a schema collision error : "pg_dump: error: options -s/--schema-only and -a/--data-only cannot be used together"

I've opened issue #104 and initialized a PR #105

[wwoytenko]

Regarding --data-only workaround right now

I recommend creating dump as usual without --data-only.

But if you need to restore only data you can call restore --data-only.

[wwoytenko]

Published in 0.1.14. Let me know if everything is ok