183 width=262) (actual time=0.031..9.825
rows=60 loops=3)
Index Cond: (l.layertypeid = v.layertypeid)
Filter: (the_geom &&
'010300010005C054C0008056C000C054C0008056400040584000805640000000405840008056C000C054C0008056C0'::geometry)
Total runtime: 33.107 ms
-
ql/bin/psql mapdb
/usr/local/pgsql/bin/vacuumdb -d mapdb -z -v
Craig James wrote:
>
> On 2007-06-11 Christo Du Preez wrote:
>> I really hope someone can shed some light on my problem. I'm not sure
>> if this is a posgres or potgis issue.
>>
>> Anyway, we have
quot; GEOS="3.0.0rc4-CAPI-1.3.3" PROJ="Rel. 4.5.0, 22 Oct
2006" USE_STATS
Thanx for all the advice
Dave Dutcher wrote:
>> -Original Message-
>> From: Christo Du Preez
>> Sent: Monday, June 11, 2007 10:10 AM
>>
>> I have narrowed down the problem (I
Good day,
I have noticed that my server never uses indexing. No matter what I do.
As an example I took a table with about 650 rows, having a parentid
field with an index on parentid.
EXPLAIN ANALYZE
SELECT *
FROM layertype
where parentid = 300;
On my laptop the explain analyze looks like this
The actual table I noticed the problem has a million rows and it still
doesn't use indexing
Reid Thompson wrote:
> try it with a table with 650K rows...
>
> On Tue, 2007-06-12 at 15:32 +0200, Christo Du Preez wrote:
>
>> Good day,
>>
>> I have noticed tha
Yes, I have just about tried every combination of vacuum on the
database. Just to make 100% sure.
Tom Lane wrote:
> Christo Du Preez <[EMAIL PROTECTED]> writes:
>
>> On my laptop the explain analyze looks like this:
>>
>
>
>> "Index Scan using f
ch of storm waves","a surface-navigation hazard composed of
consolidated material","a surface-navigation hazard composed of
unconsolidated
material"}";"{0.00298063,0.00298063,0.00298063,0.00298063,0.00298063,0.00298063,0.00298063}";"{"a
barrier const
ntify issues I'm not even aware of
or considering at this stage.
Regards,
Christo Du Preez
---(end of broadcast)---
TIP 7: You can help support the PostgreSQL project by donating at
http://www.postgresql.org/about/donate
