Re: Warn if initdb's --sync-only option is mixed with other options

2021-10-01 Thread Daniel Gustafsson
> On 7 Jul 2021, at 15:25, Daniel Gustafsson wrote: > I doubt it's worth complicating the code for this fringe case though. This thread has stalled, and with the updated docs/help output done for this option I don't think this is worth pursuing (especially given the lack of complaints over behav

Re: Warn if initdb's --sync-only option is mixed with other options

2021-07-07 Thread Daniel Gustafsson
> On 7 Jul 2021, at 04:23, Gurjeet Singh wrote: > I'm not able to come up with an exact situation to prove this, but > this behaviour seems potentially dangerous. The user might mix the > --sync-only option with other options, but would be extremely > surprised if those other options didn't take

Warn if initdb's --sync-only option is mixed with other options

2021-07-06 Thread Gurjeet Singh
When reading through code for my previous patch [1] I realized that initdb does *not* warn users that it ignores all other options (except -D/--pgdata) if the --sync-only option is used. I'm not able to come up with an exact situation to prove this, but this behaviour seems potentially dangerous.