On Mon, 2005-08-08 at 15:30, Neil Conway wrote:
> Scott Marlowe wrote:
> > You might want to schedule analyzes to run every thirty minutes or every
> > hour.
>
> I doubt that is necessary or wise. Rerunning ANALYZE should only be
> necessary when the distribution of your data changes significan
Scott Marlowe wrote:
You might want to schedule analyzes to run every thirty minutes or every
hour.
I doubt that is necessary or wise. Rerunning ANALYZE should only be
necessary when the distribution of your data changes significantly --
e.g. after a bulk load or deletion of a lot of conten
; Ragnar Hafstað;
pgsql-general@postgresql.org
Subject: Re: [GENERAL] indexes are farked
On Tue, 2005-08-02 at 15:52, Joshua D. Drake wrote:
> Bob Pawley wrote:
> > Language reflects the character of those who use it.
> >
> > In this case, the language used also reflect
On Tue, 2005-08-02 at 15:52, Joshua D. Drake wrote:
> Bob Pawley wrote:
> > Language reflects the character of those who use it.
> >
> > In this case, the language used also reflects on the community to which
> > it is directed.
> >
> > I don't wish to be associated with a "professional" communi
On Tue, Aug 02, 2005 at 01:41:48PM -0500, Scott Marlowe wrote:
> Also, you might want to look at tuning your database. I've found that
> on machines that can cache most of their data sets, adjusting things
> like effective_cache_size and random_page_cost makes a big difference.
Also, as Ragnar Ha
On Tue, 2005-08-02 at 13:26, Dr NoName wrote:
> > When's the last time you analyzed this table? And
>
> a few hours before I posted this. vacuumdb --analyze
> also runs every night.
Were there a lot of updates / deletes between when you ran analyze and
when you ran this query? If so, you might
> When's the last time you analyzed this table? And
a few hours before I posted this. vacuumdb --analyze
also runs every night.
> have you considered
> running the pg_autovacuum daemon, which will vacuum
> and analyze for you
> in the back ground?
We are using postgresql 7.3.2 which doesn't hav
On Tue, 2005-08-02 at 13:05, Dr NoName wrote:
> siam_production=> explain analyze select * from render
> where person_id = 432;
>
> QUERY PLAN
>
siam_production=> explain analyze select * from render
where person_id = 432;
QUERY PLAN
--
Seq Scan on render (cost=0.00..39014.72 rows=27
On Tue, 2005-08-02 at 12:04, Dr NoName wrote:
> Hi all,
>
> I got another problem with postgres. This time it
> refuses to use the indexes. Check this out:
>
>
> siam_production=> \d render
> Table
> "public.render"
> Column|
10 matches
Mail list logo
