Using --schema flag for having dump schema level granularity like in pg_dump and introduce --sample_schema overtaking old functionality

[andilabs]

Hi @mla !

Thanks for the awesome job you have done by delivering that nice tool ;-)

I found it very useful. I have an idea for improvement (just have to grasp a bit of Perl):

• let --schema param does behave the same as in pg_dump (best if not very complicated alow multiple repetitions of --schema or short -n to follow the pg_dump naming to specify multiple schemas to be considered by the script)
• and --sample_schema takes responsibility for current --schema functionality of pg_sample.

tell me what do you think about, what limitations (both Perl and Postgres), edge cases should I consider when tackling that issue?

Another thing for improvement sharing probably a common codebase will be support for --table level granularity.

[andilabs]

very early version andilabs#1

[mla]

Hey, @andilabs! Great, thank you. Sorry for the delay in responding, I've been traveling. I'll take a look asap. Offhand, my only concern is backwards compatibility if we're changing the --schema option. It was dumb of me to have used --schema for that.

So if we change this and ppl use --schema with the old intention, then it should normally just fail with schema not found, I would hope. Maybe we issue a warning by default if the --schema option is used and there's no --quiet added or something.

[andilabs]

Hi @mla I made further improvements and created PR #14