ERR ORR writes:
> My understanding from your replies is that this behavior with *b-tree
> indices* is not considered a bug but rather a case of "works as designed",
> yet still and apart from the solution of my particular problem, the fact
> that in 9.2.4 it is so bad that a simple query sometimes
ERR ORR wrote:
> the fact that in 9.2.4 it is so bad that a simple query sometimes
> does not finish after 10+ minutes with incessant disk activity
> tends to look like a problem to me.
Try running a VACUUM FREEZE ANALYZE; command on the database, under
a database superuser ID. If you upgraded
On 7 April 2013 15:52, Kevin Grittner wrote:
> David Johnston wrote:
>
> > varchar(100)
>
> > The other option to index words via the full-text search capabilities.
>
> Or for columns this short, a similarity search on a trigram index.
>
> http://www.postgresql.org/docs/current/interactive/pgtr
David Johnston wrote:
> varchar(100)
> The other option to index words via the full-text search capabilities.
Or for columns this short, a similarity search on a trigram index.
http://www.postgresql.org/docs/current/interactive/pgtrgm.html
--
Kevin Grittner
EnterpriseDB: http://www.enterpris
r d-3 wrote
> Hi,
>
> this is with 9.2.4_PGDG / FC18 / 64bit upgraded from 9.1.8 via
> dump/restore, settings kept for the most part.
>
> Table has 1.5M records, the varchar(100) field in question has a *
> varchar_ops* and a *varchar_pattern_ops* btree index.
>
> 3 Cases:
>
>- "MYFIELD" li
