pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Y Sidhu <ysidhu@gmail.com>
To: Jim C. Nasby <decibel@decibel.org>
Cc: pgsql-performance@postgresql.org
Subject: Re: pg_stats how-to?
Date: Mon, 14 May 2007 13:53:10 -0700
Message-ID: <b09064f30705141353p4f502135s5409c8c31c20718e@mail.gmail.com> (raw)
In-Reply-To: <20070514190748.GY69517@nasby.net>
References: <4647B0A9.7080304@gmail.com>
	<bf54be870705131751g32e29447l4ec3a2bfabca10e6@mail.gmail.com>
	<b09064f30705140916o7c1d1a24h2bdabd3714df2187@mail.gmail.com>
	<20070514162610.GO69517@nasby.net>
	<b09064f30705140928x6b44f03dtdb93ebd18e7cdaca@mail.gmail.com>
	<20070514174558.GS69517@decibel.org>
	<b09064f30705141109m7c2f57an802f8fe0485a65bb@mail.gmail.com>
	<20070514183615.GW69517@nasby.net>
	<b09064f30705141202o2cd183d7ta6914da150f3f503@mail.gmail.com>
	<20070514190748.GY69517@nasby.net>

My immediate problem is to decrease vacuum times.

Yudhvir
=======

On 5/14/07, Jim C. Nasby <decibel@decibel.org> wrote:
>
> On Mon, May 14, 2007 at 12:02:03PM -0700, Y Sidhu wrote:
> > I am sorry about this Jim, please understand that I am a newbie and am
> > trying to solve long vacuum time problems and get a handle on speeding
> up
> > queries/reports. I was pointed to pg_stats and that's where I am at now.
> I
>
> Well, I have no idea what that person was trying to convey then. What
> are you trying to look up? Better yet, what's your actual problem?
>
> > have added this into my conf file:
> >  stats_start_collector TRUE  stats_reset_on_server_start FALSE
> > stats_command_string TRUE
> > However, these being production servers, I have not enabled these:
> >  stats_row_level  stats_block_level
> FYI, stats_command_string has a far larger performance overhead than any
> of the other stats commands prior to 8.2.
>
> > Yes, I have re-started the server(s). It seems like I query tables to
> get
> > the info. If so, are there any queries written that I can use?
> >
> > Thanks for following up on this with me.
> >
> > Yudhvir
> >
> > ===
> > On 5/14/07, Jim C. Nasby <decibel@decibel.org> wrote:
> > >
> > >On Mon, May 14, 2007 at 11:09:21AM -0700, Y Sidhu wrote:
> > >> The stats_block_level and stats_row_level are NOT enabled. The
> question
> > >is
> > >> how to use pg_stats. Do I access/see them via the ANALYZE command? or
> > >using
> > >> SQL. I cannot find any document which will get me started on this.
> > >
> > >Ok, we're both confused I think... I thought you were talking about the
> > >pg_stat* views, which depend on the statistics collector (that's what
> > >the stats_* parameters control).
> > >
> > >That actually has nothing at all to do with pg_stats or pg_statistics.
> > >Those deal with statistics about the data in the database, and not
> about
> > >statistics from the engine (which is what the pg_stat* views do...).
> > >
> > >If you want to know about pg_stats, take a look at
> > >http://www.postgresql.org/docs/8.2/interactive/view-pg-stats.html ...
> > >but normally you shouldn't need to worry yourself about that. Are you
> > >trying to debug something?
> > >
> > >Information about the backend statistics can be found at
> > >http://www.postgresql.org/docs/8.2/interactive/monitoring.html
> > >--
> > >Jim Nasby                                      decibel@decibel.org
> > >EnterpriseDB      http://enterprisedb.com      512.569.9461 (cell)
> > >
> >
> >
> >
> > --
> > Yudhvir Singh Sidhu
> > 408 375 3134 cell
>
> --
> Jim Nasby                                      decibel@decibel.org
> EnterpriseDB      http://enterprisedb.com      512.569.9461 (cell)
>



-- 
Yudhvir Singh Sidhu
408 375 3134 cell

view thread (18+ messages)  latest in thread

Message-ID: <b09064f30705141353p4f502135s5409c8c31c20718e@mail.gmail.com>
Permalink:  ../b09064f30705141353p4f502135s5409c8c31c20718e@mail.gmail.com/
Also on:    postgresql.org/message-id/b09064f30705141353p4f502135s5409c8c31c20718e@mail.gmail.com

 · 

reply

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: ysidhu@gmail.com, decibel@decibel.org
  Subject: Re: pg_stats how-to?
  In-Reply-To: <b09064f30705141353p4f502135s5409c8c31c20718e@mail.gmail.com>
  References: <4647B0A9.7080304@gmail.com> <bf54be870705131751g32e29447l4ec3a2bfabca10e6@mail.gmail.com> <b09064f30705140916o7c1d1a24h2bdabd3714df2187@mail.gmail.com> <20070514162610.GO69517@nasby.net> <b09064f30705140928x6b44f03dtdb93ebd18e7cdaca@mail.gmail.com> <20070514174558.GS69517@decibel.org> <b09064f30705141109m7c2f57an802f8fe0485a65bb@mail.gmail.com> <20070514183615.GW69517@nasby.net> <b09064f30705141202o2cd183d7ta6914da150f3f503@mail.gmail.com> <20070514190748.GY69517@nasby.net> <b09064f30705141353p4f502135s5409c8c31c20718e@mail.gmail.com>

* 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