Re: [HACKERS] PG7.4 ordering operator

2003-11-20 Thread Tom Lane
strk <[EMAIL PROTECTED]> writes: > I've provided a default btree operator class but I'm often > going out of memory when using DISTINCT or UNION clauses. > How can I reduce memory usage in these cases ? > Since passed argument are TOASTED, but I use only a small > initial portion if them to make

Re: [HACKERS] PG7.4 ordering operator

2003-11-20 Thread strk
tgl wrote: > strk <[EMAIL PROTECTED]> writes: > > Testing postgis support in PG7.4 (2003-11-11) > > I've encountered to this problem: > > ERROR: could not identify an ordering operator for type geometry > > Previous PG versions does not show this problem. > > Any hint on what might be miss

Re: [HACKERS] PG7.4 ordering operator

2003-11-19 Thread Tom Lane
strk <[EMAIL PROTECTED]> writes: > Testing postgis support in PG7.4 (2003-11-11) > I've encountered to this problem: > ERROR: could not identify an ordering operator for type geometry > Previous PG versions does not show this problem. > Any hint on what might be missing ? A default btree

[HACKERS] PG7.4 ordering operator

2003-11-19 Thread strk
Testing postgis support in PG7.4 (2003-11-11) I've encountered to this problem: ERROR: could not identify an ordering operator for type geometry HINT: Use an explicit ordering operator or modify the query. Whenever I issue one of these commands: gis=# select the_geom fr