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 1sqp0u-00D6qF-RA for pgsql-docs@arkaria.postgresql.org; Wed, 18 Sep 2024 07:22:14 +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 1sqp0u-005FJX-AV for pgsql-docs@arkaria.postgresql.org; Wed, 18 Sep 2024 07:22:12 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sqp0s-005FGV-WB for pgsql-docs@lists.postgresql.org; Wed, 18 Sep 2024 07:22:12 +0000 Received: from fout8-smtp.messagingengine.com ([103.168.172.151]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sqp0o-001mWo-Ca for pgsql-docs@lists.postgresql.org; Wed, 18 Sep 2024 07:22:10 +0000 Received: from phl-compute-06.internal (phl-compute-06.phl.internal [10.202.2.46]) by mailfout.phl.internal (Postfix) with ESMTP id D28401380208; Wed, 18 Sep 2024 03:22:04 -0400 (EDT) Received: from phl-mailfrontend-01 ([10.202.2.162]) by phl-compute-06.internal (MEProxy); Wed, 18 Sep 2024 03:22:04 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eisentraut.org; h=cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm3; t=1726644124; x=1726730524; bh=mgWtdA/+E3b+vToX4cv7rilkj3lQtUkWgOGQO1RgJ/Y=; b= ebKSgRQGRf+TKNfU0nHEpQfxvIaIWo2vyTShlSEu43dJX7d/KiGQ7+cEjJxOBQaX GPXQ/aky/j8Iyd3Ze+20KsVxWu131FrnNYKoovQz4GQzVU2VnhI7XbDxNzmBqAUy Kdbq4utgEdpGoTO8GSlAQCqWMTkEUMhOILmYjkvwqvlvtINkPLfEthxp9D9MkKC2 LMj07eyBuxowuNYn9WuqkGby+79TkFVlppn8zsc1ZZefiET8wSq1Z66banBcoVgG MnHN+v3KtIn5ehZa9Zhlof4hSMxOsUEpx+Ty204r3W2vrr1EFCAYbVeUPgN6tXfT 7vF5iXNxEyPA1Jhc6/sKsQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t=1726644124; x= 1726730524; bh=mgWtdA/+E3b+vToX4cv7rilkj3lQtUkWgOGQO1RgJ/Y=; b=F kqf1c4dgqGxfJt4yrHnxPOQK5Tm0RA1nxwsCIkg+dwfhBfHa9DI3LJv69xMzcmTf zkxUEBPasANKU69RJCip+xq6Hmd4W9ztAFSsJjrRu+ViUCpTs59+nobZfIzcgMMn mHjMPfXsV+7sl5ytrP2XTMXuMMiw0vkRrQDx5pEIw4PzD0g00oPPI9wve8RMgmvj sv5zcujPYwT7R0gdMmNaZvHYnFgifeSoKZQzGL97oppnfjzmKm2yBhIIjyJd6Lyg W4FZoRABZlcH71EPQWFrdyPDKNtmhmRcAbkNwYAtsnfxcjtXfb7P19PHxVCNPaR+ k4VF/3Hi0Cm5busvvcjnw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeftddrudekkedguddvtdcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpggftfghnshhusghstghrihgsvgdp uffrtefokffrpgfnqfghnecuuegrihhlohhuthemuceftddtnecunecujfgurhepkfffgg gfuffvfhfhjggtgfesthejredttddvjeenucfhrhhomheprfgvthgvrhcugfhishgvnhht rhgruhhtuceophgvthgvrhesvghishgvnhhtrhgruhhtrdhorhhgqeenucggtffrrghtth gvrhhnpeegueeuvdfhheeuieejtefguddthfevveefuefgtddvgfetteehjeetleeuvdev udenucffohhmrghinhepphhoshhtghhrvghsqhhlrdhorhhgnecuvehluhhsthgvrhfuih iivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepphgvthgvrhesvghishgvnhhtrhgr uhhtrdhorhhgpdhnsggprhgtphhtthhopedvpdhmohguvgepshhmthhpohhuthdprhgtph htthhopegrmhhinhesghhilhgrnhhirdhmvgdprhgtphhtthhopehpghhsqhhlqdguohgt sheslhhishhtshdrphhoshhtghhrvghsqhhlrdhorhhg X-ME-Proxy: Feedback-ID: ie0a040ee:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 18 Sep 2024 03:22:03 -0400 (EDT) Message-ID: <21ff4e12-0b59-4062-be22-f89c6e69773f@eisentraut.org> Date: Wed, 18 Sep 2024 09:22:02 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Elaborate on phrase "table metadata" in the Notes section of ALTER by specifying pg_attribute To: amin@gilani.me, pgsql-docs@lists.postgresql.org References: <172608553929.1128079.5845807167540849323@wrigleys.postgresql.org> Content-Language: en-US From: Peter Eisentraut In-Reply-To: <172608553929.1128079.5845807167540849323@wrigleys.postgresql.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 11.09.24 22:12, PG Doc comments form wrote: > Page:https://www.postgresql.org/docs/16/sql-altertable.html > Description: > > I am newish to Postgres, and the term "table metadata" was confusing to > me. I think it is pretty easy to do a quick internet search to find out what table metadata is in the context of an SQL database. Your complaint isn't wrong in the sense that the term isn't formally defined here, but in this case I would opt against adding more text and leave it up to the user to do the extra research as necessary. The operation being discussed isn't something a completely new user would immediately encounter, after all. > > I am more than happy to submit a patch for this. I'm just unfamiliar with > the process. Please advise. > >> When a column is added with ADD COLUMN and a non-volatile DEFAULT is > specified, the default is evaluated at the time of the statement and the > result stored in the table's metadata. That value will be used for the > column for all existing rows. If no DEFAULT is specified, NULL is used. In > neither case is a rewrite of the table required. > > Specifically this sentence: "the result stored in the table's metadata" > > Suggest adding specific language to correct it to "the result stored in the > table's metadata. See `pg_attribute` for more information." >