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 1pT5Oa-0004Ve-KI for pgsql-bugs@arkaria.postgresql.org; Fri, 17 Feb 2023 18:23:44 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pT5OZ-00077A-Bq for pgsql-bugs@arkaria.postgresql.org; Fri, 17 Feb 2023 18:23:43 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pT5OZ-000771-3S for pgsql-bugs@lists.postgresql.org; Fri, 17 Feb 2023 18:23:43 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pT5OW-0001fY-Pj for pgsql-bugs@lists.postgresql.org; Fri, 17 Feb 2023 18:23:42 +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 31HINcaV2713024; Fri, 17 Feb 2023 13:23:38 -0500 From: Tom Lane To: Samo Dadela cc: pgsql-bugs@lists.postgresql.org Subject: Re: pg_restore: warning: could not find where to insert IF EXISTS in statement "-- *not* dropping schema, since initdb creates it In-reply-to: References: Comments: In-reply-to Samo Dadela message dated "Fri, 17 Feb 2023 12:21:25 +0100" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2713022.1676658218.1@sss.pgh.pa.us> Date: Fri, 17 Feb 2023 13:23:38 -0500 Message-ID: <2713023.1676658218@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Samo Dadela writes: > Can you please take a look at the following? > It's just a warning - the restore succeeded anyway. > pg_restore is emitting the following: > pg_restore: warning: could not find where to insert IF EXISTS in statement > "-- *not* dropping schema, since initdb creates it This was reported already, and is fixed in 15.2. regards, tom lane