Re: [PATCH] Unify duplicate-option handling across utility commands

From: Álvaro Herrera <alvherre(at)kurilemu(dot)de>
To: Baji Shaik <baji(dot)pgdev(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: [PATCH] Unify duplicate-option handling across utility commands
Date: 2026-10-07 18:31:04
Message-ID: asaPplEeWXT6JnFc@alvherre.pgsql
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2026-Oct-07, Baji Shaik wrote:

> Based on that, I'm leaning towards last-wins rather than erroring on
> duplicate options. It matches what REPACK/VACUUM/EXPLAIN already do, and
> REPACK was recently fixed in-tree to be last-wins.

Oh, it was? I don't remember that -- where is that? I don't think
last-wins is our norm, or is it?

--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
"In fact, the basic problem with Perl 5's subroutines is that they're not
crufty enough, so the cruft leaks out into user-defined code instead, by
the Conservation of Cruft Principle." (Larry Wall, Apocalypse 6)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bharath Rupireddy 2026-10-07 18:34:40 Re: WAL segment file descriptor leak on read errors can PANIC the server
Previous Message Peter Eisentraut 2026-10-07 17:58:35 Re: fix more casting away of qualifiers