Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1c1SYl-0000si-IU for pgsql-performance@arkaria.postgresql.org; Tue, 01 Nov 2016 06:28:35 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1c1SYl-0003Zz-3o for pgsql-performance@arkaria.postgresql.org; Tue, 01 Nov 2016 06:28:35 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1c1SX5-0001k5-Pd for pgsql-performance@postgresql.org; Tue, 01 Nov 2016 06:26:51 +0000 Received: from mail-lf0-x234.google.com ([2a00:1450:4010:c07::234]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1c1SWy-0003Ql-T2 for pgsql-performance@postgresql.org; Tue, 01 Nov 2016 06:26:50 +0000 Received: by mail-lf0-x234.google.com with SMTP id b81so119022028lfe.1 for ; Mon, 31 Oct 2016 23:26:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-transfer-encoding:mime-version:subject:message-id:date :to; bh=r5L6Me5MI7zappHcDkhrJaL/unWuX4M56ri+L/HImuY=; b=xddTAhd/7U8ZcCW9r19EW0nqAXkCrjXJVPuuGBjEsXCtS/9aDxflBJcZkGG7OGrGWD x/KuD+nVzJAAL9pNeZljXCCs8DVrCQfDEuCKz1Gf1DIqPje58gDvJmCVqqARti1lW+Yt 5YcgjVh/mG3iYBtsYMIFJWok+AfuqzVfjBwV/u3hp5bRaX9keIjpxtWxz0LAsK8HSiou SNHPnOSVtMiOsF6DiXgP2anzjZ4XAKt9dPse9W+J95Wvy613+Gu+XKzBAD2OAf9+wTKf DETSob4k82FzGRFKiukmvxke7JWElzOz8OP4nojtx/C+kqBUnZPRnJkUQHaMZoATuWvT inlw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:message-id:date:to; bh=r5L6Me5MI7zappHcDkhrJaL/unWuX4M56ri+L/HImuY=; b=cNaBbncYhGXUNGdxWBkXzt3hqdHoD6LmL3dbnirgNcQ/QO2Y0qyUoG7y9JL9J5gjw2 1RjlotsGvFTgcYf7onJjSQ9KHWCA0IcfQDcES65il1NgYHxV2UZkvU4eJsKK8rq0Xs8D Y21pebLC42sPFgDloX3N/mV+AuQe4yFvAwwm1zOQtIoXBIhp1xjCJOPYLVxqKrkxXwoL Kng7j41wb6vtE5wI52e9B10aePAPwIbsK/Xc3L4qHhKkcB+we8M6dD4xKQPJUXZrclQB jId4B8e6aoBTWsNpl1k5RZD9f0i4VHiv0zxtHx76C20I0ahJJJu28azCIJI7C9YQ4nX2 5kwQ== X-Gm-Message-State: ABUngvc4qrPPADIx3NsX5Zgp4gKuC8MJGapxjRaJL++ZZmWHAwkK3mFCCpVyfXzWnyFijQ== X-Received: by 10.25.212.136 with SMTP id l130mr19523231lfg.73.1477981601777; Mon, 31 Oct 2016 23:26:41 -0700 (PDT) Received: from [10.108.1.99] ([109.195.102.122]) by smtp.gmail.com with ESMTPSA id l70sm116040lfl.30.2016.10.31.23.26.40 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 31 Oct 2016 23:26:41 -0700 (PDT) From: =?utf-8?B?0JDQvdGC0L7QvSDQnNCw0LfRg9C90LjQvQ==?= Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.1 \(3251\)) Subject: Refresh materialized view vs recreate Message-Id: Date: Tue, 1 Nov 2016 11:26:42 +0500 To: "pgsql-performance@postgresql.org" X-Mailer: Apple Mail (2.3251) X-Pg-Spam-Score: -2.7 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-performance Precedence: bulk Sender: pgsql-performance-owner@postgresql.org Hello!=20 We have a situation when after creation of new materialized view cpu utiliz= ation falls down (from about 50% to about 30%), at the same time we have a = cron job, which does refresh of old materialized view, but it does no effec= t at performance. Can anyone explain why is it so? And what is the difference between refresh= and create new? --=20 Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance