Did this change to gistsplit.c to reduce the logging from LOG down to
DEBUG1 ever done?
--
Tim Wilson
Lead DB Engineer - Telogis
www.telogis.com www.telogis.co.nz
+1 201 477-1448 (USA) +64 3 339-2825 (NZ)
*One Platform for Location Intelligence*
—
This e-mail, and any attachments, is intended
Yes, thanx. This would be useful as some of our clients are getting
swamped (and confused) with these messages in the log files.
Cheers,
Kevin
Tom Lane wrote:
Teodor Sigaev <[EMAIL PROTECTED]> writes:
Split page algorithm was rewrited for 8.2 for multicolumn indexes and API for
user-define
Teodor Sigaev <[EMAIL PROTECTED]> writes:
> Split page algorithm was rewrited for 8.2 for multicolumn indexes and API for
> user-defined pickSplit function was extended to has better results with index
> creation. But GiST can interact with old functions - and it says about this.
> That isn't me
Split page algorithm was rewrited for 8.2 for multicolumn indexes and API for
user-defined pickSplit function was extended to has better results with index
creation. But GiST can interact with old functions - and it says about this.
That isn't mean some real problem or error - index will be the
Has anyone come across this error before?
LOG: PickSplit method of 2 columns of index
'asset_position_lines_asset_cubespacetime_idx' doesn't support secondary
split
This is a multi-column GiST index on an integer and a cube (a data type
from the postgres cube extension module).
I traced t
