Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1gC7Dz-0001vN-OC for pgsql-admin@arkaria.postgresql.org; Mon, 15 Oct 2018 18:04:15 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gC7Dx-00050W-VP for pgsql-admin@arkaria.postgresql.org; Mon, 15 Oct 2018 18:04:13 +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.89) (envelope-from ) id 1gC7Dx-00050E-KP for pgsql-admin@lists.postgresql.org; Mon, 15 Oct 2018 18:04:13 +0000 Received: from mx.ssan.egs-seg.gc.ca ([205.193.229.132]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gC7Dr-0006BJ-Lv for pgsql-admin@postgresql.org; Mon, 15 Oct 2018 18:04:11 +0000 Received: from DC01ZWH0020.paz.nrc.gc.ca ([167.37.58.16]) by mx.ssan.egs-seg.gc.ca with ESMTP id w9FI44hH004380-w9FI44hJ004380 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=CAFAIL) for ; Mon, 15 Oct 2018 14:04:04 -0400 Received: from DC01ZWH0015.Corp.nrc.gc.ca (167.37.54.209) by DC01ZWH0020.paz.nrc.gc.ca (167.37.58.16) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Mon, 15 Oct 2018 14:04:01 -0400 Received: from DC01ZWH0014.Corp.nrc.gc.ca (167.37.54.208) by DC01ZWH0015.Corp.nrc.gc.ca (167.37.54.209) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Mon, 15 Oct 2018 14:04:03 -0400 Received: from DC01ZWH0014.Corp.nrc.gc.ca ([167.37.54.208]) by DC01ZWH0014.Corp.nrc.gc.ca ([167.37.54.208]) with mapi id 15.00.1347.000; Mon, 15 Oct 2018 14:04:03 -0400 From: "Ghiurea, Isabella" To: "pgsql-admin@postgresql.org" Subject: effective_cache_size cfg Thread-Topic: effective_cache_size cfg Thread-Index: AQHUZLBgsJy5jlikc0SgYkOfs0pzDg== Date: Mon, 15 Oct 2018 18:04:03 +0000 Message-ID: <1539626643680.56712@nrc-cnrc.gc.ca> Accept-Language: en-US, en-CA Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [167.37.48.8] Content-Type: multipart/alternative; boundary="_000_153962664368056712nrccnrcgcca_" MIME-Version: 1.0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --_000_153962664368056712nrccnrcgcca_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello List, I am running PGSQL 10.4 on Cent OS Pg instance has ' effective_cache_size= ' parameter not enabled I would like to learn what will the optimizer beh= avior be in this case ? ( default is set to 4GB , I was thinking PG 's optimizer will try to use= all available OS RAM when trying to estimate a query, is this the case) thank you Isabella --_000_153962664368056712nrccnrcgcca_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Hello List,

I am running PGSQL 10.4  on Cent OS  Pg instance has = ;' effective_cache_size' parameter not  enabled I would like to learn = what will  the optimizer behavior be in this case ?

 ( default is set to 4GB , I was  thinking  PG 's optimiz= er will try to use all available OS RAM when trying to estimate a query, is= this the case)


thank you

Isabella

--_000_153962664368056712nrccnrcgcca_--