Re: anybody know who the damn list owner is? RE: Postgresql ism & Vacuum? - Mailing list pgsql-general

From Andy Lewis
Subject Re: anybody know who the damn list owner is? RE: Postgresql ism & Vacuum?
Date
Msg-id Pine.LNX.4.20.0004141140550.15979-100000@mail.recruitersonline.com
Whole thread Raw
In response to anybody know who the damn list owner is? RE: Postgresql ism & Vacuum?  ("Oelkers, Phil" <phil.oelkers@experian.com>)
List pgsql-general
For starters I head over to www.postgresql.org

Then I'd probably click on the "Info Central" link and then the "Mailing
lists" link.

From there I'd click on the list that I was subscribed to under "Mailing
List Archives"

Then I'd read the info at the top of the page.....

Those pages haven't really changed in content in years....



On Fri, 14 Apr 2000, Oelkers, Phil wrote:

> I've been trying to get off this list forever no luck.  I thought
> I got the damn thing set to nomail, still get mail.
>
> DOES ANYBODY KNOW WHERE I CAN CONTACT A
> LIKE PERSON TO GET OFF THIS DAMN LIST?
>
> > -----Original Message-----
> > From:    Peter Eisentraut [SMTP:e99re41@DoCS.UU.SE]
> > Sent:    Friday, April 14, 2000 6:59 AM
> > To:    Thomas
> > Cc:    pgsql-general@postgresql.org
> > Subject:    Re: [GENERAL] Postgresqlism & Vacuum?
> >
> > On Fri, 14 Apr 2000, Thomas wrote:
> >
> > > I think there must be something wrong with the optimiser that it's
> > > "postgresqlism" that you must vacuum analyze frequently.
> >
> > One thing that is not widely known is that vacuum actually has two
> > orthogonal tasks: garbage collection and statistics collection (only when
> > you ANALYZE). The fact that this is combined in one command is a
> > historical artifact, and there are some voices that want to separate the
> > commands.
> >
> > The way I see it, if you have enough disk space you never have to run
> > vacuum to garbage collect. It might lead to obvious problems when the heap
> > files get so large that it takes more time to physically access them. The
> > alternative is to garbage collect on each transaction commit but that
> > bears its own set of performance implications.
> >
> > The analyze part would probably not need an exclusive lock on the table
> > but the vacuum certainly does.
> >
> >
> > --
> > Peter Eisentraut                  Sernanders v�g 10:115
> > peter_e@gmx.net                   75262 Uppsala
> > http://yi.org/peter-e/            Sweden
>


pgsql-general by date:

Previous
From: Ed Loehr
Date:
Subject: Re: anybody know who the damn list owner is? RE: Postgresqlism & Vacuum?
Next
From: The Hermit Hacker
Date:
Subject: Comments requested on "Site Search" ...