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 1hXlCN-0000oH-Ub for pgsql-admin@arkaria.postgresql.org; Mon, 03 Jun 2019 11:32:20 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hXlCM-00070w-KF for pgsql-admin@arkaria.postgresql.org; Mon, 03 Jun 2019 11:32:18 +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 1hXlCM-00070p-8i for pgsql-admin@lists.postgresql.org; Mon, 03 Jun 2019 11:32:18 +0000 Received: from mail-ot1-x341.google.com ([2607:f8b0:4864:20::341]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hXlCJ-0006Yn-QJ for pgsql-admin@lists.postgresql.org; Mon, 03 Jun 2019 11:32:17 +0000 Received: by mail-ot1-x341.google.com with SMTP id l17so15735479otq.1 for ; Mon, 03 Jun 2019 04:32:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=oe2LL6ubP9cRCLKWS3wy2wRvkfx5EjqoPtqZ9Wgjbfg=; b=o3CBMX1WQOCtKx53qi7l8fuj08ZTSc/fdhzoewWCY+eSR6xpcndhgcaeXTsSgEubL4 7KNBYfiHRKcDdgQeugpU/p1X4dKhWWFy4IPnN4HGedwrptMHFYphnt6VtgYctdnhyFdh mZs3XCmwLUY5wGGcD0mZjW40z1qZkiTmBlyEA6D2TRlVpT3VxJlQ4TDJa5/Zs0YU3zBG oU4yhYQLdBXN9ifZN6oTLtoUlxHAeMBkHoiP0tgPsFbsgFu2i2BZsdUAyleWSnGZkZ/P Gy3bsS3sbADS8KJmyjA89ZjtjjG+8YwSqaquxNH0De1NztemRNspa1ODwzoI/cbNWO8y ghsg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=oe2LL6ubP9cRCLKWS3wy2wRvkfx5EjqoPtqZ9Wgjbfg=; b=gmkZ5/2kZzHpVRIDZPvLPWNrvKTvpEWi9hriMvpE1q3sdrncGtWysKPrzPKPBoLHW4 h+XcZyy6LbJNTrQuIR1moc7ixW9dHR7D4chpM1JHUtaGQ5Lbxp29v4RIEo3d1rddCcRh +slhI5YqMzbeSfaI6epDY6FWj3S3V6PqZ5AuIcXeoNrIWsA+7jCCMzoQMyDXWiHI4L6V lQCOUZozqqUUHYxzx+piVrsnQvnzfGlwHaa7+tKpzo+WmtjaoBXBJDi1o9wT5/ceNBFR UrFnL7yx1zHn7z5hAccmb31ihShT1snzc95t+TPzK1+m7EQJXSPxwlVVRB/ls48UfYsw BURA== X-Gm-Message-State: APjAAAUyr9a+RsJ4ItII2jA2NoeKL8P3VCdnfBluJ6LlB8fKaZ7aIEEP pU9MFNsbeXySHF8ApLR2lqr5216S3jo= X-Google-Smtp-Source: APXvYqznc2C6DyYTvwW5ywjgMdvuSnGq2KMZXy9J2hfxcq/svWL/oyP8YFbM42yvRjCYK/Xt29/2Tg== X-Received: by 2002:a9d:e8e:: with SMTP id 14mr754161otj.87.1559561533497; Mon, 03 Jun 2019 04:32:13 -0700 (PDT) Received: from [192.168.1.10] (ip70-171-116-89.no.no.cox.net. [70.171.116.89]) by smtp.googlemail.com with ESMTPSA id r20sm3187114oij.49.2019.06.03.04.32.12 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 03 Jun 2019 04:32:12 -0700 (PDT) Subject: Re: ERROR:::::: could not rename temporary statistics file ... To: pgsql-admin@lists.postgresql.org References: <2A91BEF8171A5349931391E0C721CC533D53302F@CPEMS-KPN301.KPNCNL.LOCAL> <7afa9150-e79e-b016-4618-d7df23211d62@gmail.com> <2A91BEF8171A5349931391E0C721CC5344508B6A@CPEMS-KPN501.KPNCNL.LOCAL> From: Ron Message-ID: <6c314d1a-e662-af06-03a3-fc504a9702bb@gmail.com> Date: Mon, 3 Jun 2019 06:32:12 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: <2A91BEF8171A5349931391E0C721CC5344508B6A@CPEMS-KPN501.KPNCNL.LOCAL> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Please don't top-post. On 6/3/19 6:26 AM, soumik.bhattacharjee@kpn.com wrote: > My pg_restore is stuck here for last 2 days. > > pg_restore: creating CONSTRAINT "schema_name.num_servicenummer_historie snh_prx" Consuming CPU and disk IO, or just sitting there? > -----Original Message----- > From: Ron > Sent: Monday, June 03, 2019 1:24 PM > To: pgsql-admin@lists.postgresql.org > Subject: Re: ERROR:::::: could not rename temporary statistics file ... > > On 6/3/19 4:46 AM, soumik.bhattacharjee@kpn.com wrote: >> Hello, >> >> While doing a restore from pgadmin, getting the below error- it's like 12GB restore file. >> >> Any pointers to solve this issue. >> >> >> >> 2019-06-03 09:01:39.978 UTC [17] LOG: could not rename temporary statistics file "pg_stat_tmp/db_13015.tmp" to "pg_stat_tmp/db_13015.stat": No such file or directory >> 2019-06-03 09:01:40.090 UTC [17] LOG: could not rename temporary statistics file "pg_stat_tmp/global.tmp" to "pg_stat_tmp/global.stat": No such file or directory > That's a LOG level message, not an ERROR level message.  Does Postgres not work? > > -- Angular momentum makes the world go 'round.