Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1isKKe-0005SZ-6k for pgsql-bugs@arkaria.postgresql.org; Fri, 17 Jan 2020 05:38:08 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1isKKc-0004W8-R9 for pgsql-bugs@arkaria.postgresql.org; Fri, 17 Jan 2020 05:38:06 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1isKKc-0004W0-Iz for pgsql-bugs@lists.postgresql.org; Fri, 17 Jan 2020 05:38:06 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1isKKV-0000p2-6q for pgsql-bugs@lists.postgresql.org; Fri, 17 Jan 2020 05:38:06 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id 00H5btUJ004218; Fri, 17 Jan 2020 00:37:55 -0500 From: Tom Lane To: shurutov@gmail.com cc: pgsql-bugs@lists.postgresql.org Subject: Re: BUG #16214: Settings is not copy In-reply-to: <16214-aee287cfd82762b4@postgresql.org> References: <16214-aee287cfd82762b4@postgresql.org> Comments: In-reply-to PG Bug reporting form message dated "Fri, 17 Jan 2020 04:23:56 +0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <4216.1579239475.1@sss.pgh.pa.us> Date: Fri, 17 Jan 2020 00:37:55 -0500 Message-ID: <4217.1579239475@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk PG Bug reporting form writes: > Than I made copy as "CREATE DATABASE demo_small template demo", after this I > noticed: > ... > Parameter "search_path" was not copied. CREATE DATABASE is not defined to copy database-level properties, only the contents of the database. As it says in the manual, this is not really intended as a general-purpose database copying command in the first place. For its intended purpose, copying database-level properties wouldn't be particularly desirable. Certainly you wouldn't want it to clone the database's ownership or ACL. regards, tom lane