Re: wildcard makes seq scan on prod db but not in test

On 5/9/11 8:57 , Kevin Grittner wrote:
>
> That could be a difference is collations.  What do you get from the
> query on this page for each database?:
>
> http://wiki.postgresql.org/wiki/Server_Configuration
>
> -Kevin
>
>
There's indeed a different collation. Why is this affecting? Can i force
a column to be ascii?

The (fast) test server:
  version              | PostgreSQL 9.0.4 on x86_64-apple-darwin10.7.0,
compiled by GCC i686-apple-darwin10-gcc-4.2.1 (GCC) 4.2.1 (Apple Inc.
build 5664), 64-bit
  effective_cache_size | 512MB
  lc_collate           | C
  lc_ctype             | UTF-8
  maintenance_work_mem | 128MB
  max_connections      | 100
  max_stack_depth      | 2MB
  port                 | 5435
  server_encoding      | UTF8
  shared_buffers       | 512MB
  temp_buffers         | 8192
  TimeZone             | Europe/Zurich
  wal_buffers          | 1MB
  work_mem             | 128MB
(14 rows)

The (slow) production server:
  version                      | PostgreSQL 9.0.4 on
x86_64-unknown-linux-gnu, compiled by
GCC gcc (Debian 4.3.2-1.1) 4.3.2, 64-bit
  checkpoint_completion_target | 0.9
  checkpoint_segments          | 64
  effective_cache_size         | 48GB
  lc_collate                   | en_US.UTF-8
  lc_ctype                     | en_US.UTF-8
  listen_addresses             | localhost,10.0.0.3,74.50.57.76
  maintenance_work_mem         | 1GB
  max_connections              | 600
  max_stack_depth              | 2MB
  port                         | 5435
  server_encoding              | UTF8
  shared_buffers               | 8GB
  temp_buffers                 | 32768
  TimeZone                     | UTC
  work_mem                     | 128MB
(16 rows)

Thanks,
Marcus