Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bjl6Q-0002R2-O8 for pgsql-admin@arkaria.postgresql.org; Tue, 13 Sep 2016 10:38:10 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bjl6Q-0002IV-Af for pgsql-admin@arkaria.postgresql.org; Tue, 13 Sep 2016 10:38:10 +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 1bjl4j-0000Gw-Ix for pgsql-admin@postgresql.org; Tue, 13 Sep 2016 10:36:25 +0000 Received: from mail-wm0-x234.google.com ([2a00:1450:400c:c09::234]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1bjl4g-0007kn-WE for pgsql-admin@postgresql.org; Tue, 13 Sep 2016 10:36:24 +0000 Received: by mail-wm0-x234.google.com with SMTP id b187so179299315wme.1 for ; Tue, 13 Sep 2016 03:36:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:subject:from:reply-to:to:cc:date:in-reply-to:references :mime-version; bh=EmmqG//zlmx08LOvgXyTupv5Nwp1ywPwCQzYHONQZEw=; b=0Zwp7dD+2lEOfeJqZO56NGktROtt/vqz5vTmzyr/TbwwQNw6jyfVX6ZbB0K1FF19kz I2qgAHEh9l24F9tM/f6G3IDp2miRFfeHqJ54/+Bdr1tKstEEJoO0ZX1rHW4syF+3Oirm h02wgN2v20w1ORwMqswvVxgH9dJUSmOPEgt/aZw2hgiFGaCbDblrAyFL1yGYKmqY8QzN TTWpW0+PCZyx22RjRDHVF/Z66JOL4H3mqv4C70Uo0shXSzPntNAWgEShenO0aIPoOR4U GzYrbxuyamsoSUiecj80igBhz/gRSxW2VG8sgaBIv6emXZFKUzzin8i9tO9NBYXtz3oD dAYw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:subject:from:reply-to:to:cc:date :in-reply-to:references:mime-version; bh=EmmqG//zlmx08LOvgXyTupv5Nwp1ywPwCQzYHONQZEw=; b=d6WlxUhap+2uBShRc7DH/qFCvnsfdQcavO6/rC5iWGkNxYZcRhz4YDnVweZacVOXWK 3UfWKtR1PToGYEjHhhauHrjWKCxi84lE1RpLlnYEdwJXVFfkCKQQT61e6MQmQC/sYyKC NEVZpg1saSijDoTi2nUk6kYow9P4MnRnaGNyVzrSWJMApxOmDeTvdVKx3ARqodT0P1A1 PazFWY2YRTl3TUvvD06N3kng4Hwubnn8K9ifzdV39AF/wkPLXfL2UaCImyiUnqJa4jgU hW0njM3TcvIt3wDBbj6Nc41lgA3TpA4ypF98fAqqHehhm1bJ+iuAEcp2NYpXEnB/3XeM 6epQ== X-Gm-Message-State: AE9vXwM2fdv18ByhVldbx7zhCttEzcqxjQmC4dCxFk0hPCvBgxpTwoMq153+/XzQxGF9WA== X-Received: by 10.194.241.227 with SMTP id wl3mr666431wjc.177.1473762981422; Tue, 13 Sep 2016 03:36:21 -0700 (PDT) Received: from enterprisedb01 (27.red-213-96-140.staticip.rima-tde.net. [213.96.140.27]) by smtp.googlemail.com with ESMTPSA id nd1sm17328067wjb.22.2016.09.13.03.36.19 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 13 Sep 2016 03:36:19 -0700 (PDT) Message-ID: <1473762979.896.3.camel@gmail.com> Subject: Re: Autovacuum Running Timeframe From: jaime soler Reply-To: jaime.soler@gmail.com To: Gaetano Mendola , Amar , =?UTF-8?Q?=CE=9A=CE=BF=CE=BA=CE=BC=CE=AC=CE=B4=CE=B7=CF=82_?= =?UTF-8?Q?=CE=94=CE=B7=CE=BC=CE=AE=CF=84=CF=81=CE=B9=CE=BF=CF=82?= Cc: pgsql-admin@postgresql.org Date: Tue, 13 Sep 2016 12:36:19 +0200 In-Reply-To: References: Content-Type: multipart/alternative; boundary="=-/HW9jfFx3227ZDUaIpLR" X-Mailer: Evolution 3.18.5.2-0ubuntu3 Mime-Version: 1.0 X-Pg-Spam-Score: -2.7 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org --=-/HW9jfFx3227ZDUaIpLR Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit El lun, 12-09-2016 a las 22:39 +0000, Gaetano Mendola escribió: > Are you sure, that's not the recommended use. I also don't recommend to disable autovacuum why don't you programme a batch task that executes vacuum in  low activity hours > > On Mon, Sep 5, 2016, 11:46 Amar wrote:> > Hi > > Dimitris, > > I would suggest to manually schedule database > > vacuum using cron jobs, instead of relaying on auto-vacuum. > > Regards, > > Amar > > On Mon, Sep 5, 2016 at 10:41 AM, Κοκμάδης Δημήτριος > > > > wrote: > > > Hello, > > > > > > I have a problem with autovacuum  > > > > > > It runs randomly, so when it runs in websites high traffic hours it causes problems with site speed. > > > > > > Is it possible to define specific timezone when autovacuum process could run? > > > > > > Regards, > > > > > > Dimitris  > > > > > > > > > -- > > ~Amar > > > --=-/HW9jfFx3227ZDUaIpLR Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable
El lun, 12-09-2016 a las 22:39 +0000, Gaetano= Mendola escribi=C3=B3:

Are y= ou sure, that's not the recommended use.


I also don't recommend to disable autovacuum why don't you programme a b= atch task that executes vacuum in  low activity hours


On Mon, Sep 5, 2016, 11:46 = Amar <amarno1@gmail.com> wro= te:
Hi Dimitris,

I would suggest to = manually schedule database vac= uum using cron jobs, instead of relaying on auto-vacuum.
<= div>
Regards,
Amar

On Mon, Sep 5, 2016 at 10:41 AM, = =CE=9A=CE=BF=CE=BA=CE=BC=CE=AC=CE=B4=CE=B7=CF=82 =CE=94=CE=B7=CE=BC=CE=AE= =CF=84=CF=81=CE=B9=CE=BF=CF=82 <dkokmadis@gmail.com> wrote= :
Hello,

<= /div>
I have a problem with autovacuum 

I= t runs randomly, so when it runs in websites high traffic hours it causes p= roblems with site speed.

Is it possible to define = specific timezone when autovacuum process could run?

Regards,

Dimitris 




--
~Amar

--=-/HW9jfFx3227ZDUaIpLR--