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 1sMnl6-004fGd-NL for pgsql-hackers@arkaria.postgresql.org; Thu, 27 Jun 2024 11:57:49 +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 1sMnl5-009oUR-1h for pgsql-hackers@arkaria.postgresql.org; Thu, 27 Jun 2024 11:57:47 +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 1sMnl3-009oUJ-JG for pgsql-hackers@lists.postgresql.org; Thu, 27 Jun 2024 11:57:47 +0000 Received: from fout6-smtp.messagingengine.com ([103.168.172.149]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sMnl0-003oi9-0z for pgsql-hackers@postgresql.org; Thu, 27 Jun 2024 11:57:45 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailfout.nyi.internal (Postfix) with ESMTP id BFFB013805EF; Thu, 27 Jun 2024 07:57:39 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Thu, 27 Jun 2024 07:57:39 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eisentraut.org; h=cc: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=fm1; t=1719489459; x=1719575859; bh=8oDSXCI8ozCy5f1NGE1L4tJOWPW2LARE uiGTT1llDvI=; b=TBMQV264Bkkvvqnrf1/Cb7t4ALB/Wa7lo2lTsVetN2WE0Frt jovrMj/i1wFcHiycE9ZU3bJo8h5AllVfSzEhqtbNW90XEWauDqIVwBJTw59JHNZa jg19fuMtts+pNulxWuHBINUEy8rRa6Y4bKoUfVUwAgN8r7fljTvnhTFywovR5Bi6 x5k1loj7XQ4PNIPTVCCfa0uYSej+R4Q8kwvdnT+rJJ2icyxsjM+6N/8BC6yF71tp jCSMVHS2tKzn2xCYE8OFItBItNa+9ViQficDoPEFdgU4JSjv0CDGTR1A7sgIzKnB xMxtx0eHYKLGVLe4ZsjbqaKSj4QCxkghvjOjcA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc: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=fm2; t=1719489459; x= 1719575859; bh=8oDSXCI8ozCy5f1NGE1L4tJOWPW2LAREuiGTT1llDvI=; b=P /jATFHUacsUvvRuXY8ZnUaZ8LDiNiEtT4vFFKv1FyhLgVoTcBt181RnFRm7l0vhl GA726shNcj+zodF+OKE2LsTnxytgxX3jQfCw9x7r/fc9p9HJAo9TZLMvL+n8h/GY tuIkcwQeqqVNiallquWF+EiB1snK0C9TvB8PsOhJBlUiYvV/tas/oLqu/kACDmSO yBvO1bqkt/VuHxfy7xyed+JsEcfexUd6LogHLZ/XN4dQ75NKLc7dqMR+KnWX2s+c Big7KL2cO/4TvRA6gMhWHM2bCppjeo9tLRn8vgRLthCGqrviFg4fqhqP58KY0rHR pfIaDqK5mB5h1tZIoeU2g== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeftddrtdeggdegiecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefkffggfgfuvfevfhfhjggtgfesthejredttddvjeenucfhrhhomheprfgvthgv rhcugfhishgvnhhtrhgruhhtuceophgvthgvrhesvghishgvnhhtrhgruhhtrdhorhhgqe enucggtffrrghtthgvrhhnpefgjedthfekfedtuefgieelheetleejgefhueeltdfhueet vdffudekfeejhfegheenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrih hlfhhrohhmpehpvghtvghrsegvihhsvghnthhrrghuthdrohhrgh X-ME-Proxy: Feedback-ID: ie0a040ee:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 27 Jun 2024 07:57:38 -0400 (EDT) Message-ID: Date: Thu, 27 Jun 2024 13:57:37 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Should we document how column DEFAULT expressions work? To: David Rowley , Tom Lane Cc: "David G. Johnston" , James Coleman , pgsql-hackers References: <1362410.1719349169@sss.pgh.pa.us> <1390099.1719357084@sss.pgh.pa.us> <1642803.1719447063@sss.pgh.pa.us> Content-Language: en-US From: Peter Eisentraut In-Reply-To: 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 27.06.24 02:34, David Rowley wrote: > For the special timestamp stuff, that place is probably the special > timestamp table in [1]. It looks like the large caution you added in > 540849814 might not be enough or perhaps wasn't done soon enough to > catch the people who read that part of the manual before the caution > was added. Hard to fix if it's the latter without a time machine. :-( Maybe we should really be thinking about deprecating these special values and steering users more urgently toward more robust alternatives. Imagine if 'random' were a valid input value for numeric types.