On Wed, 26 Mar 2025 at 02:05, Euler Taveira <eu...@eulerto.com> wrote: > > On Tue, Mar 25, 2025, at 8:07 AM, Shubham Khanna wrote: > > The following code is not accurate. If I specify --all, --database and > --subscription, it will report only --database. The user will remove it and > run > again. At this time, --subscription will be report. My expectation is to have > all reports at once.
I felt pg_dump reports conflicts incrementally rather than listing all incompatible options at once as shown below: ### Specified, --data-only, --schema-only, --statistics-only, --no-data and --clean options. together Example1: ./pg_dump --data-only --schema-only --statistics-only --no-data --clean -d postgres -f dump.txt pg_dump: error: options -s/--schema-only and -a/--data-only cannot be used together ### After removing --schema-only option, another error arises Example2: ./pg_dump --data-only --statistics-only --no-data --clean -d postgres -f dump.txt pg_dump: error: options -a/--data-only and --statistics-only cannot be used together ### After removing --no-data option, another error arises Example3: ./pg_dump --data-only --no-data --clean -d postgres -f dump.txt pg_dump: error: options -a/--data-only and --no-data cannot be used together ### After removing --clean option, another error arises Example4: ./pg_dump --data-only --clean -d postgres -f dump.txt pg_dump: error: options -c/--clean and -a/--data-only cannot be used together I believe the current patch follows this approach and also simplifies the code handling, making it easier to maintain. Regards, Vignesh
