pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Adrian Klaver <adrian.klaver@aklaver.com>
To: postgann2020 s <postgann2020@gmail.com>
To: pgsql-general@postgresql.org
To: pgsql-admin@postgresql.org
To: pgsql-performance@postgresql.org
Subject: Re: Suggestion on table analyze
Date: Thu, 21 May 2020 07:41:37 -0700
Message-ID: <0a0225d9-0e21-413f-8230-93a197748bde@aklaver.com> (raw)
In-Reply-To: <CANynezMbVr894sUocUkw0_nWgKeBVUn+xqaW_vL=c3OOYd1w8Q@mail.gmail.com>
References: <CANynezMbVr894sUocUkw0_nWgKeBVUn+xqaW_vL=c3OOYd1w8Q@mail.gmail.com>

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





view thread (3+ messages)  latest in thread

Message-ID: <0a0225d9-0e21-413f-8230-93a197748bde@aklaver.com>
Permalink:  ../0a0225d9-0e21-413f-8230-93a197748bde@aklaver.com/
Also on:    postgresql.org/message-id/0a0225d9-0e21-413f-8230-93a197748bde@aklaver.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: adrian.klaver@aklaver.com, postgann2020@gmail.com, pgsql-general@postgresql.org, pgsql-performance@postgresql.org
  Subject: Re: Suggestion on table analyze
  In-Reply-To: <0a0225d9-0e21-413f-8230-93a197748bde@aklaver.com>
  References: <CANynezMbVr894sUocUkw0_nWgKeBVUn+xqaW_vL=c3OOYd1w8Q@mail.gmail.com> <0a0225d9-0e21-413f-8230-93a197748bde@aklaver.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox