Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jbmOJ-0007eJ-J6 for pgsql-admin@arkaria.postgresql.org; Thu, 21 May 2020 14:41:48 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jbmOI-0000vQ-Hf for pgsql-admin@arkaria.postgresql.org; Thu, 21 May 2020 14:41:46 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jbmOG-0000vF-V6; Thu, 21 May 2020 14:41:46 +0000 Received: from wout2-smtp.messagingengine.com ([64.147.123.25]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jbmOD-0000Ou-AE; Thu, 21 May 2020 14:41:43 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id 61968C79; Thu, 21 May 2020 10:41:39 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Thu, 21 May 2020 10:41:39 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= subject:to:references:from:message-id:date:mime-version :in-reply-to:content-type:content-transfer-encoding; s=fm3; bh=G DueoVVm/dS1J89J9gCdc+Td+vqo5rjDAL/q2OhNvTI=; b=eflsiSSI0okOjvYU6 EfS4nHarFarl1iytYIbd2LM5pEzRbyuNYXIrckjLXm6dPo+JwVV+jzZHnmQGFJ7N jT/vSphFF73iGwAfahZlHyaFs23+isV4Wx+xD3jvRF6yvgpiG7B1F7QfM9lI7NSK 7nHX+PilE2WSIGU6dKSxG0g2JMmfxdK5Ww+g1SqRtEGmRzP/0CSwrdBih3KmV9jS RH4rOhhhzuW517lqWTVdu1qHXRRGIyUg0i9tClwy/dnkJBzjnhMSE+bW81e5OykP IUambuPdO3ivvT35Ox+iAbPncSvuJeUIXgEiiL5YJh0ETySBDskz6adfTTdgIkIg uxA+w== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=GDueoVVm/dS1J89J9gCdc+Td+vqo5rjDAL/q2OhNv TI=; b=SEBQU5kavmhar1lS4RlXv8vD8UxT4G7C/yjP/k4+QLVHNcgGWRQhAZ7/T vskNMEcrQwGYirEKXrDJSV1xb4vlfFU9ik8+OM0Jy0DMiLzPfDxhJiwpWQZprg/R Sgp1QDVcNGfjYHmbaMuPKxW4CQdnnD4QEkNviES3HVdseh3bAsYXMoiho1Esgp++ T9ZJ6MnrtuEXWxv9+OchhsfJ5X9uKr5mgziXlOnun8nFWKH6Ix39T2Mj3PPCCoZp KquKxEAaZxDR9i38OBq0L1Zj+KSxal7ahdxwDCjpNBR0LUFTFtZWnu/eFMjoXIhz SQ/xe10Y01V4FJFWkVVPUtYTwetqA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedrudduuddgjeekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepuffvfhfhkffffgggjggtgfesthekredttdefjeenucfhrhhomheptegurhhi rghnucfmlhgrvhgvrhcuoegrughrihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrdgtoh hmqeenucggtffrrghtthgvrhhnpeegheeuffetieefhffgledttdetfeetjeehkedvkefg keeiteevvdevteehveekkeenucffohhmrghinhepphhoshhtghhishdrnhgvthenucfkph epjeehrddujedvrdehrddvfedunecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghm pehmrghilhhfrhhomheprggurhhirghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtghomh X-ME-Proxy: Received: from [192.168.1.3] (75-172-5-231.tukw.qwest.net [75.172.5.231]) by mail.messagingengine.com (Postfix) with ESMTPA id 416A4306648C; Thu, 21 May 2020 10:41:38 -0400 (EDT) Subject: Re: Suggestion on table analyze To: postgann2020 s , pgsql-general@postgresql.org, pgsql-admin@postgresql.org, pgsql-performance@postgresql.org References: From: Adrian Klaver Message-ID: <0a0225d9-0e21-413f-8230-93a197748bde@aklaver.com> Date: Thu, 21 May 2020 07:41:37 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 5/21/20 7:18 AM, postgann2020 s wrote: > Hi Team, > > Thanks for your support. > > Could you please suggest on below query. > > Environment > PostgreSQL: 9.5.15 > Postgis: 2.2.7 > > Mostly table contain GIS data. > > While analyzing the table getting below NOTICE. It seems is pretty > understanding, but needs help on the below points. > > 1 . What might be the reason for getting the NOTICE?. > 2. Is this lead to any problems in the future?. > > ANALYZE SCHEMA.TABLE; > > NOTICE:  no non-null/empty features, unable to compute statistics > NOTICE:  no non-null/empty features, unable to compute statistics > Query returned successfully with no result in 1.1 secs. This is coming from PostGIS: postgis/gserialized_estimate.c: /* If there's no useful features, we can't work out stats */ if ( ! notnull_cnt ) { elog(NOTICE, "no non-null/empty features, unable to compute statistics"); stats->stats_valid = false; return; } You might find more information from here: https://postgis.net/support/ Though FYI PostGIS 2.2.7 is past EOL: https://postgis.net/source/ > > Thanks for your support. > > Regards, > PostgAnn. -- Adrian Klaver adrian.klaver@aklaver.com