Re: what is the cause that scan type is showing as 'seq scan' after

From: "Glenn Wiorek" <gwiorek(at)jmlafferty(dot)com>
To: "Gaetano Mendola" <mendola(at)bigfoot(dot)com>, <pgsql-admin(at)postgresql(dot)org>
Cc: "Joseph Lemm" <joelemm(at)yahoo(dot)com>
Subject: Re: what is the cause that scan type is showing as 'seq scan' after
Date: 2004-01-05 14:35:19
Message-ID: 004101c3d399$24b6e990$143264c8@jmlafferty.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Also take a look at Annotated postgresql.conf and Global User Configuration
(GUC) Guide

http://www.varlena.com/GeneralBits/Tidbits/annotated_conf_e.html

----- Original Message -----
From: "Gaetano Mendola" <mendola(at)bigfoot(dot)com>
To: <pgsql-admin(at)postgresql(dot)org>
Cc: "Joseph Lemm" <joelemm(at)yahoo(dot)com>
Sent: Monday, January 05, 2004 8:26 AM
Subject: Re: [ADMIN] what is the cause that scan type is showing as 'seq
scan' after

> Joseph Lemm wrote:
>
> > Gaetano, thanks.
> >
> > My db has only one table (about 29,000 records), so I thought leaving
> > postgreqsql.conf at its defaults would be OK: the params you mention are
> > commented out, so they must be at their defaults, tho I can't tell what
the
> > defaults are.
>
> The values on the line commented are the default values.
>
> > Are there any docs that talk specificially about how to set these params
and
> > what the defaults are (the official docs don't say much)?
>
>
> Take a look at performance NG, at least is what I use to do.
>
>
>
> Regards
> Gaetano Mendola
>
>
>
>
>
>
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
>
>

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Tsirkin Evgeny 2004-01-05 14:48:00 Re: postgresql crushed with XLogWrite error
Previous Message ma101csn 2004-01-05 14:26:04 Query