Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qnfcu-00Bb75-2W for pgsql-bugs@arkaria.postgresql.org; Tue, 03 Oct 2023 13:39:52 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qnfcs-005ntT-Gn for pgsql-bugs@arkaria.postgresql.org; Tue, 03 Oct 2023 13:39:50 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qnfcs-005nso-4n for pgsql-bugs@lists.postgresql.org; Tue, 03 Oct 2023 13:39:50 +0000 Received: from mail-wm1-x336.google.com ([2a00:1450:4864:20::336]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qnfcp-007z8m-Tx for pgsql-bugs@lists.postgresql.org; Tue, 03 Oct 2023 13:39:49 +0000 Received: by mail-wm1-x336.google.com with SMTP id 5b1f17b1804b1-4066241289bso9089805e9.0 for ; Tue, 03 Oct 2023 06:39:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec-at.20230601.gappssmtp.com; s=20230601; t=1696340266; x=1696945066; darn=lists.postgresql.org; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:to:from:subject:message-id:from:to:cc:subject:date :message-id:reply-to; bh=DBXVASmUgv2vOi74VXDQkwK9Ff3qt4sYuqNlvYND+Mg=; b=IoVsu0uqzVnyUMyI9OoA+GRCmJoHPuoZs0i1PMIJMOJ49nWeJvDCof4EVeJlnD8uN0 Y47fMfRRE94IYMpuHzJ8lcjYFkIfqvr7J8G7ZUeQShmrX99GDs0NThq62Apn+A3TLn5Z Je1JTRniVXZngU978QlorcRIvdhYYDDM9PAkeMoHW3IZBAMC5k/Er864HZ+xZTAWKqLX zXMUE1VUCayoXJK5+dLsb6oDUO88YsMmGEXanqApKw6V8XhNQ/mgY2aY2LY5KD/tVwMT OAfD2Jd3lnuD9fZIwWBYHfHF6p9oZNaO+z6hCBCfHdGInPBXHODlsRacByBfve4Nxdtl A1yQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1696340266; x=1696945066; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:to:from:subject:message-id:x-gm-message-state:from :to:cc:subject:date:message-id:reply-to; bh=DBXVASmUgv2vOi74VXDQkwK9Ff3qt4sYuqNlvYND+Mg=; b=rmjM6NA70nXtj/dzcoOGRQnzAhxmIl3Nf0uAMpw0b4hOX5jDByQwVAxNtYZzkuiiGM 3yyuq/EBx9fX/Sf+w83V/gGpssVJD7YDsDheyNQ9ADFUMyRvYg3qLVT/fv5MdVrDeqpA F8GCvzPIrm0G9XPTH6VnzMrUy2CyfMvg9rGwChiI1kYoagdamMQzHoY2md8LOpPg7EiI 6MRsOUjoBY8EOiDd3t4nkHh7Mlbm8CiLh4P9XUdXm3YVd48rYEuYyLFljSkmS7R106kW 3jFQewFRpvNIV4CWoxOs5aTKGsjlpjWjddAyJ0I64o93c0v5uCqpYdgd7nipTfXSbR/q hV0w== X-Gm-Message-State: AOJu0Yz1Rw42VPmQvVfR/30Pq8fGFNVLDrghPf2RsQxEyH5UBOhWP0Cv woCteswXjtWVEUd/N850nbeaEiPGCU+/l+b9S6Q= X-Google-Smtp-Source: AGHT+IFr8ImcXUDMirmN8DkWOcd7V54GMBV9tTF0LJVe/XDRALBk7noEsbaGFXkQClQVs63Ruq8+Wg== X-Received: by 2002:adf:ea8f:0:b0:320:4cf:5b50 with SMTP id s15-20020adfea8f000000b0032004cf5b50mr14357498wrm.5.1696340266465; Tue, 03 Oct 2023 06:37:46 -0700 (PDT) Received: from localhost.localdomain ([2001:871:5e:1c0:45b9:97:dde5:9bad]) by smtp.gmail.com with ESMTPSA id 9-20020a05600c234900b00405c7591b09sm1302714wmq.35.2023.10.03.06.37.46 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 03 Oct 2023 06:37:46 -0700 (PDT) Message-ID: Subject: Re: BUG #18145: In psql, \d does not output in expanded format From: Laurenz Albe To: robert.nilsson.123@gmail.com, pgsql-bugs@lists.postgresql.org Date: Tue, 03 Oct 2023 15:37:45 +0200 In-Reply-To: <18145-5da930760e745493@postgresql.org> References: <18145-5da930760e745493@postgresql.org> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.48.4 (3.48.4-1.fc38) MIME-Version: 1.0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Tue, 2023-10-03 at 03:39 +0000, PG Bug reporting form wrote: > PostgreSQL version: 16.0 > Operating system:=C2=A0=C2=A0 Ubuntu 11.4.0 (x86_64) >=20 > Turn on expanded output > database=3D> \x on >=20 > Display the information about the table again: > database=3D> \d test > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0 Table "pg_temp_6.test" > =C2=A0Column |=C2=A0 Type=C2=A0=C2=A0 | Collation | Nullable | Default > --------+---------+-----------+----------+--------- > =C2=A0id=C2=A0=C2=A0=C2=A0=C2=A0 | integer |=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 |=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0 | >=20 > Expected to see output in expanded format, like this; > Table "pg_temp_6.test" > -[ RECORD 1 ]------ > Column=C2=A0=C2=A0=C2=A0 | id > Type=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 | integer > Collation | > Nullable=C2=A0 | > Default=C2=A0=C2=A0 | >=20 > The related command \dt works as expected; I don't think that's a bug. \dt just prints a result set, which is easy to render in expanded mode. But \d prints many other things (indexes, foreign keys, storage parameters,= ...), and it is not clear how that should look in expanded mode. Yours, Laurenz Albe