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 1sPpy8-006ZTH-N5 for pgsql-hackers@arkaria.postgresql.org; Fri, 05 Jul 2024 20:55:48 +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 1sPpy6-00EBNv-J6 for pgsql-hackers@arkaria.postgresql.org; Fri, 05 Jul 2024 20:55: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 1sPpy6-00EBNn-9a for pgsql-hackers@lists.postgresql.org; Fri, 05 Jul 2024 20:55:46 +0000 Received: from momjian.us ([72.94.173.45]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sPpy4-000c6v-UX for pgsql-hackers@postgresql.org; Fri, 05 Jul 2024 20:55:46 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=momjian.us; s=2024011501; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:Cc:To:From:Date:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description; bh=QC7odIHUtfhdL4AQTCnDH62ig41fKc5MzjuHw2m6Bt8=; b=lMIOK ShdSVm29M9tLnBGvSJj77fWKlvZdAR6Bu49a2zgQzyqidMzW6xAlG34UHihIgXppMgEOk85noCf2Z S1uttodWX6u9XijyPoBcay/TzTAu1HqFlP5ptbLVfyBF3hyocCw668pV+Yj+GqpQV03+pVl8fcxrW hGyrFTo5YpGx09XPzBhWilzJ9VEJ6SLc6OTqrh+nU1HXl2mDnyDlu7bfsQG0LCjdL06LzO3i1ETHc bUQi33wGcpLlyO3FT5XWMOKNgMa/1r7kjdjAnbCk6+k++gkJu42gAblz+z8Ooo8qgcYuzdHIynXBS 87HjLNZaXJS4KMXyoECAPIgq0xumw==; Received: from bruce by momjian.us with local (Exim 4.96) (envelope-from ) id 1sPpy2-008lDP-1g; Fri, 05 Jul 2024 16:55:42 -0400 Date: Fri, 5 Jul 2024 16:55:42 -0400 From: Bruce Momjian To: Tom Lane Cc: David Rowley , "David G. Johnston" , Peter Eisentraut , James Coleman , pgsql-hackers Subject: Re: Should we document how column DEFAULT expressions work? Message-ID: References: <1642803.1719447063@sss.pgh.pa.us> <342046.1720212632@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <342046.1720212632@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Fri, Jul 5, 2024 at 04:50:32PM -0400, Tom Lane wrote: > Bruce Momjian writes: > > Also interestingly, "now" without quotes requires parentheses to make it > > a function call: > > I'm not sure why you find that surprising, or why you think that > 'now()'::timestamptz is a function call. (Well, it is a call of > timestamptz_in, but not of the SQL function now().) Documentation > that is equally confused won't help any. Well, 'now()' certainly _looks_ like a function call, though it isn't. The fact that 'now()'::timestamptz and 'now'::timestamptz generate volatile results via a function call was my point. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Only you can decide what is important to you.