Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: simple case using index on windows but not on linux
- From: "simon godden" <sgodden(at)gmail(dot)com>
- To: "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com>
- Cc: pgsql-performance(at)postgresql(dot)org
- Subject: Re: simple case using index on windows but not on linux
- Date: Wed, 4 Oct 2006 10:19:01 +0100
- Message-id: <168519350610040219n648a282hf159ff272e0f672a(at)mail(dot)gmail(dot)com>
(Sending again because I forgot to reply to all) On 10/4/06, Heikki Linnakangas <heikki(at)enterprisedb(dot)com> wrote:
You can increase the max shared memory size if you have root access. See http://www.postgresql.org/docs/8.1/interactive/kernel-resources.html#SYSVIPC-PARAMETERS Scroll down for Linux-specific instructions.
Thanks for the link. Are you saying that the shared memory size is the issue here? Please can you explain how it would cause a seq scan rather than an index scan. I would like to understand the issue before making changes. -- Simon Godden
- Follow-Ups:
- Re: simple case using index on windows but not on linux
- From: Richard Huxton
- Re: simple case using index on windows but not on linux
- References:
- simple case using index on windows but not on linux
- From: simon godden
- Re: simple case using index on windows but not on linux
- From: Heikki Linnakangas
- simple case using index on windows but not on linux
- Prev by Date: Re: simple case using index on windows but not on linux
- Next by Date: Re: simple case using index on windows but not on linux
- Previous by thread: Re: simple case using index on windows but not on linux
- Next by thread: Re: simple case using index on windows but not on linux
- Indexes: