[HACKERS] timestamp parse error
Hello! i'm using PostgreSQL 7.2.1 and got strange parse errors.. could somebody tell me what's wrong with this timestamp query example? PostgreSQL said: ERROR: parser: parse error at or near date Your query: select timestamp(date '1998-02-24', time '23:07') example is from PostgreSQL help and certainly worked in previous versions of pgsql.. but in 7.2.1 it does not. had anything changed and not been updated in pgsql manuals or is it a bug? thanx for any help Tomas Lehuta ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
[HACKERS] contrib/fulltextindex
Hello! i've got a question on my problem.. i'm using contrib/fulltextindex to index my tables to do a fulltext search but i'm using a non-default locale settings on my database. i found out that if the locale is default 'C' then fulltextindex tables are scanned very fast using btree indices. for sure, i'm using prefix match (string ~ '^blabla') which is supposed to scan the table in this way.. so it's ok! but if i change to different locale (i.e. sk_SK or cs_CZ) the fti table is scanned sequentially and it's very slow.. so, the more words are there in my fti table and the more more words i'm trying to search at once using table join the slower is the search.. so my question is.. is this a bug or the prefix match is not supported to perform a table scan using indices under non-default locale? please, give me a hint.. regards Tomas Lehuta ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
[HACKERS] contrib/fulltextindex
Hello! i've got a question on my problem.. i'm using contrib/fulltextindex to index my tables to do a fulltext search but i'm using a non-default locale settings on my database. i found out that if the locale is default 'C' then fulltextindex tables are scanned very fast using btree indices. for sure, i'm using prefix match (string ~ '^blabla') which is supposed to scan the table in this way.. so it's ok! but if i change to different locale (i.e. sk_SK or cs_CZ) the fti table is scanned sequentially and it's very slow.. so, the more words are there in my fti table and the more more words i'm trying to search at once using table join the slower is the search.. so my question is.. is this a bug or the prefix match has no support to perform a table scan using indices under non-default locale? please, give me a hint.. regards Tomas Lehuta ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
