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 1glsa1-000443-PS for pgsql-admin@arkaria.postgresql.org; Tue, 22 Jan 2019 09:42:49 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1glsa0-0007Lh-JM for pgsql-admin@arkaria.postgresql.org; Tue, 22 Jan 2019 09:42:48 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1glsa0-0007LX-5U for pgsql-admin@lists.postgresql.org; Tue, 22 Jan 2019 09:42:48 +0000 Received: from mail-lj1-x22f.google.com ([2a00:1450:4864:20::22f]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1glsZy-0000yV-1T for pgsql-admin@lists.postgresql.org; Tue, 22 Jan 2019 09:42:46 +0000 Received: by mail-lj1-x22f.google.com with SMTP id v15-v6so19927502ljh.13 for ; Tue, 22 Jan 2019 01:42:45 -0800 (PST) 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-language:content-transfer-encoding; bh=rz493hFWFk36kWQGejVVPKzLbQoqsQDMnCp+zsD6XGk=; b=kDqA2O31gU4r2LaVgP1exFKbgzW43KOPGZZ5+kIHpgRrvdF3NCz6kRUALzauz8o4/U velh80PpwKouALvZZ4b9XXYJkcgWHMEF5HkCO53Nlp8GHB4TRRiVyJSMnASQTmkwZnF0 locYJpObIPPklOaiyF2tG5uPkdZExR31NMOMeLk38wkLAbK1aO+b3Qn8mjUpx2GIccPw wucKHsXcTaPANVpbw33L7mwFsCt6x/TCjEVDNPJBEVh/CMYQxC5a3rmjcnINzVn5QHt0 8uJzBWpWl071n8A6vGlcSRjedU1d5/wTgti77OPPXSR8uP7Ybt6RNjXCzbeVIxp7XKCo dgFg== 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-language :content-transfer-encoding; bh=rz493hFWFk36kWQGejVVPKzLbQoqsQDMnCp+zsD6XGk=; b=Bt5zJVx/YVzzOxDSIpzteH0D6vslgTac/EezF7eFAnXGnktqwmhvanvekpR6AJkcRR 8tO8AqaflyAvCMhoh01HLL/7Di+gAFrWcA0RRtBAQuc7CsGtnR83NGG39I3PoQ2AVd7v gbAi10kPQTeSpDg/ECj/XHPbl4ZcZ9VZj32AVFjPRuqI9V5Kr2HKiKcNBcDlJThxt6mx Esfe8yPwEvHXS3buvo0JcO1OY0EVl3YOXZ9E3cbzUMq6FUU+nTLksb+kndQOdRBhnRv4 8qGl/WX0DNOkV+zG5hEuIrnexjOuplBGWeupkFMSeyw+Be8ZzUKnpdUXc6WYxsOlJnJw tjAA== X-Gm-Message-State: AJcUukeGye8vx3d/5rQzx+EYLgv1lZcOpu0Ng2Qp9fYgzFJRZGSR/7wM 244fGDAIhEIS78Pcs0oVD40vCoc0 X-Google-Smtp-Source: ALg8bN6G+OJLPmSKWjuFBsdCpeHsYsSEXDDCBvHc/NcsfvIbdX7HV8ev2SrYq2u/LGKQ4wKzHgMAbw== X-Received: by 2002:a2e:8554:: with SMTP id u20-v6mr32495ljj.193.1548150163612; Tue, 22 Jan 2019 01:42:43 -0800 (PST) Received: from [192.168.20.69] (bramka-zew.dfqs.pl. [194.126.222.22]) by smtp.googlemail.com with ESMTPSA id z2-v6sm59363ljk.50.2019.01.22.01.42.42 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 22 Jan 2019 01:42:43 -0800 (PST) Subject: Re: IO scheduler recommendation To: AB_ba# , pgsql-admin@lists.postgresql.org References: From: Andrzej Zawadzki Message-ID: <6a845a35-bb5a-bf67-1b06-b68a2a3cfbdc@gmail.com> Date: Tue, 22 Jan 2019 10:42:41 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/html; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk
On 21.01.2019 12:04, AB_ba# wrote:
Hello ,

I searched the complete PostgreSQL Documentation but didn't get anything with respect to IO scheduler recommendation.

On bare metal I'm using 'deadline'.


What is being recommended by PostgreSQL ?
Which is the best IO scheduler considering the Data is hosted on NFS?

NFS? Better use iSCSI.


--

Andrzej