From: Kevin Grittner <Kevin.Grittner@wicourts.gov>
To: Thomas Kellerer <spam_eater@gmx.net>
To: pgsql-performance@postgresql.org
Subject: Re: Select * is very slow
Date: Mon, 08 Nov 2010 11:15:56 -0600
Message-ID: <4CD7DBEC02000025000373E2@gw.wicourts.gov> (raw)
In-Reply-To: <ib9as0$a8s$1@dough.gmane.org>
References: <1289197016462-3254568.post@n5.nabble.com>
<4CD7D89A02000025000373D8@gw.wicourts.gov>
<ib9as0$a8s$1@dough.gmane.org>
Thomas Kellerer <spam_eater@gmx.net> wrote:
> Kevin Grittner, 08.11.2010 18:01:
>> I would add a request to see the output from `VACUUM VERBOSE
>> employee;`.
> Do you really think that VACCUM is the problem? If the OP only
> selects two columns it is apparently fast.
> If he selects all columns it's slow, so I wouldn't suspect dead
> tuples here.
>
> My bet is that there are some really large text columns in
> there...
That's something we can infer pretty well from the verbose output.
-Kevin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: Kevin.Grittner@wicourts.gov, spam_eater@gmx.net
Subject: Re: Select * is very slow
In-Reply-To: <4CD7DBEC02000025000373E2@gw.wicourts.gov>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox