pg.ddx.io pgsql-sql@postgresql.org mailing list archive
help / color / mirror / Atom feedno notnull values, invalid stats?
4+ messages / 3 participants
[nested] [flat]
* no notnull values, invalid stats?
@ 2006-02-06 11:58 Markus Schaber <schabi@logix-tt.com>
2006-02-06 14:02 ` Re: no notnull values, invalid stats? Alvaro Herrera <alvherre@commandprompt.com>
0 siblings, 1 reply; 4+ messages in thread
From: Markus Schaber @ 2006-02-06 11:58 UTC (permalink / raw)
To: pgsql-sql
Hello,
The following message occasionally appears in my postgresql log - from
temporal corellation, it might be caused by autovacuum.
NOTICE: no notnull values, invalid stats
Is that anything I should care about?
I'm running debianized postgresql 8.1.0-3.
Markus
--
Markus Schaber | Logical Tracking&Tracing International AG
Dipl. Inf. | Software Development GIS
Fight against software patents in EU! www.ffii.org www.nosoftwarepatents.org
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: no notnull values, invalid stats?
2006-02-06 11:58 no notnull values, invalid stats? Markus Schaber <schabi@logix-tt.com>
@ 2006-02-06 14:02 ` Alvaro Herrera <alvherre@commandprompt.com>
2006-02-06 14:32 ` Re: no notnull values, invalid stats? Markus Schaber <schabi@logix-tt.com>
0 siblings, 1 reply; 4+ messages in thread
From: Alvaro Herrera @ 2006-02-06 14:02 UTC (permalink / raw)
To: Markus Schaber <schabi@logix-tt.com>; +Cc: pgsql-sql
Markus Schaber wrote:
> Hello,
>
> The following message occasionally appears in my postgresql log - from
> temporal corellation, it might be caused by autovacuum.
>
> NOTICE: no notnull values, invalid stats
I see no such message in 8.1 sources. Is this verbatim or did you
translate it?
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: no notnull values, invalid stats?
2006-02-06 11:58 no notnull values, invalid stats? Markus Schaber <schabi@logix-tt.com>
2006-02-06 14:02 ` Re: no notnull values, invalid stats? Alvaro Herrera <alvherre@commandprompt.com>
@ 2006-02-06 14:32 ` Markus Schaber <schabi@logix-tt.com>
2006-02-06 17:35 ` Re: no notnull values, invalid stats? Michael Fuhr <mike@fuhr.org>
0 siblings, 1 reply; 4+ messages in thread
From: Markus Schaber @ 2006-02-06 14:32 UTC (permalink / raw)
To: Alvaro Herrera <alvherre@commandprompt.com>; +Cc: pgsql-sql
Hi, Alvaro,
Alvaro Herrera wrote:
>>The following message occasionally appears in my postgresql log - from
>>temporal corellation, it might be caused by autovacuum.
>>
>>NOTICE: no notnull values, invalid stats
>
> I see no such message in 8.1 sources. Is this verbatim or did you
> translate it?
It is verbatim from /var/log/postgresql/postgresql-8.1-main.log.
But I have PostGIS installed in some of the databases, so it might be
from there.
Markus
--
Markus Schaber | Logical Tracking&Tracing International AG
Dipl. Inf. | Software Development GIS
Fight against software patents in EU! www.ffii.org www.nosoftwarepatents.org
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: no notnull values, invalid stats?
2006-02-06 11:58 no notnull values, invalid stats? Markus Schaber <schabi@logix-tt.com>
2006-02-06 14:02 ` Re: no notnull values, invalid stats? Alvaro Herrera <alvherre@commandprompt.com>
2006-02-06 14:32 ` Re: no notnull values, invalid stats? Markus Schaber <schabi@logix-tt.com>
@ 2006-02-06 17:35 ` Michael Fuhr <mike@fuhr.org>
0 siblings, 0 replies; 4+ messages in thread
From: Michael Fuhr @ 2006-02-06 17:35 UTC (permalink / raw)
To: Markus Schaber <schabi@logix-tt.com>; +Cc: Alvaro Herrera <alvherre@commandprompt.com>; pgsql-sql
On Mon, Feb 06, 2006 at 03:32:32PM +0100, Markus Schaber wrote:
> Alvaro Herrera wrote:
> >>The following message occasionally appears in my postgresql log - from
> >>temporal corellation, it might be caused by autovacuum.
> >>
> >>NOTICE: no notnull values, invalid stats
> >
> > I see no such message in 8.1 sources. Is this verbatim or did you
> > translate it?
>
> It is verbatim from /var/log/postgresql/postgresql-8.1-main.log.
>
> But I have PostGIS installed in some of the databases, so it might be
> from there.
That is indeed a PostGIS message; it's in compute_geometry_stats()
in lwgeom/lwgeom_estimate.c. I think it means that during an
analyze, all of the sampled rows had NULL values in their geometry
columns (i.e., no not-NULL values were found); that would explain
the correlation with autovacuum. Here's an example that elicits
the notice:
postgis=> CREATE TABLE foo ();
CREATE TABLE
postgis=> SELECT AddGeometryColumn('foo', 'geom', -1, 'GEOMETRY', 2);
addgeometrycolumn
------------------------------------------------
public.foo.geom SRID:-1 TYPE:GEOMETRY DIMS:2
(1 row)
postgis=> INSERT INTO foo VALUES (NULL);
INSERT 0 1
postgis=> ANALYZE foo;
NOTICE: no notnull values, invalid stats
ANALYZE
postgis=> UPDATE foo SET geom = GeomFromText('POINT(0 0)');
UPDATE 1
postgis=> ANALYZE foo;
ANALYZE
--
Michael Fuhr
^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~2006-02-06 17:35 UTC | newest]
Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2006-02-06 11:58 no notnull values, invalid stats? Markus Schaber <schabi@logix-tt.com>
2006-02-06 14:02 ` Alvaro Herrera <alvherre@commandprompt.com>
2006-02-06 14:32 ` Markus Schaber <schabi@logix-tt.com>
2006-02-06 17:35 ` Michael Fuhr <mike@fuhr.org>
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