Re: Inconsistency in psql output with \d+x PATTERN

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: George MacKerron <george(dot)mackerron(at)databricks(dot)com>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: Inconsistency in psql output with \d+x PATTERN
Date: 2026-10-19 10:09:57
Message-ID: CAHGQGwHr5b1oUNyNvvFkAsL5B0wv01wJLqFYEdQnZ61HSaTE6g@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Sat, Oct 17, 2026 at 1:16 AM George MacKerron
<george(dot)mackerron(at)databricks(dot)com> wrote:
> This inconsistency seems like a bug to me.

Sequence descriptions have honored expanded mode since v10, so disabling it
would change longstanding behavior. Also the vertical layout seems useful
for sequence descriptions, so I'd prefer to keep the current behavior and
update the documentation instead. Thought?

We could clarify that, when a name or pattern is specified, only sequence
descriptions honor expanded mode, whether enabled globally with \x on or
\x auto, or temporarily with \d+x.

Regards,

--
Fujii Masao

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Nitin Motiani 2026-10-19 11:29:58 Re: BUG #19767: pg_get_viewdef prints ORDER BY (- '3'::int4) as (- 3), which reparses as column position -3
Previous Message David Rowley 2026-10-19 08:36:25 Re: BUG #19759: Hashed SetOp / RecursiveUnion pre-allocate up to 64 GB from the row estimate since 8f29467c57f