Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lGjf4-0007qv-Pg for pgsql-bugs@arkaria.postgresql.org; Mon, 01 Mar 2021 14:36:38 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lGjf2-0007iL-55 for pgsql-bugs@arkaria.postgresql.org; Mon, 01 Mar 2021 14:36:36 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lGjf1-0007iE-VP for pgsql-bugs@lists.postgresql.org; Mon, 01 Mar 2021 14:36:35 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lGjev-0003VV-6e for pgsql-bugs@lists.postgresql.org; Mon, 01 Mar 2021 14:36:34 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 121EaQAY715799; Mon, 1 Mar 2021 09:36:26 -0500 From: Tom Lane To: java reddy cc: pgsql-bugs@lists.postgresql.org Subject: Re: After upgrade from 9.4.1-3 to 10.15 and fresh install of 10.15 have some differences in the schema definition In-reply-to: References: Comments: In-reply-to java reddy message dated "Mon, 01 Mar 2021 15:49:20 +0530" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <715797.1614609386.1@sss.pgh.pa.us> Date: Mon, 01 Mar 2021 09:36:26 -0500 Message-ID: <715798.1614609386@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk java reddy writes: > I have one fresh install and other one is upgrade path (from 94. to > 10.15).I am compare schema definitions full install versus upgrade path. > I see some differences. > 1. CURRENT_TIMESTAMP is replaced with now() > 2.('now'::text)::timestamp without time zone is replaced with > LOCAL_TIMESTAMP v10 and later preserve CURRENT_TIMESTAMP and some similar SQL-standard constructs as entered, when dumping the contents of views, column default expressions, and the like. Older versions replaced them with PG-specific equivalents. Neither behavior is a bug. regards, tom lane