Lists: | pgsql-general |
---|
From: | Oleg Mürk <oleg(dot)myrk(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Picksplit warning |
Date: | 2012-05-08 12:11:17 |
Message-ID: | CAEsn3ybKcnFno_tGQDJ=AfHiR2xd9KA1FQt5CQxxYu3Wz_hAHQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-general |
Hello,
Our postgresql logs are getting filled with warnings:
LOG: picksplit method for column COLUMN_IDX of index INDEX_NAME
doesn't support secondary split
We are using gist indexes on integer, timestamp, and Postgis geometry.
Is there a way to work around this problem?
Thank You,
Oleg Mürk
From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
---|---|
To: | Oleg Mürk <oleg(dot)myrk(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Picksplit warning |
Date: | 2012-05-30 21:06:10 |
Message-ID: | 1338411970.18825.22.camel@jdavis |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-general |
On Tue, 2012-05-08 at 15:11 +0300, Oleg Mürk wrote:
> Hello,
>
> Our postgresql logs are getting filled with warnings:
> LOG: picksplit method for column COLUMN_IDX of index INDEX_NAME
> doesn't support secondary split
> We are using gist indexes on integer, timestamp, and Postgis geometry.
>
> Is there a way to work around this problem?
http://archives.postgresql.org/pgsql-general/2007-08/msg01810.php
A similar complaint from a long time ago. It looks like the conclusion
was to demote that to a DEBUG1 message, which won't clutter your logs.
It doesn't indicate a real problem. It's essentially saying that PostGIS
is missing out on a potential optimization, which is not something you
can easily fix. It's also not very well documented, unfortunately, so
it's not something the PostGIS folks can fix easily, either. I brought
this up on -hackers, so hopefully it will be resolved.
In the meantime, you're stuck with the messages cluttering your
logfiles.
Regards,
Jeff Davis