Thread: psql 8.1.9 autovacuum safe?
Hi, We are running postgresql-8.1.9 and plan to upgrade to 8.2 or even 8.3 but can't just yet. I need to run analyze periodically (like hourly), but before I write a script to loop through the tables in each schema and run analyze, I thought I would try autovacuum. I say one post that said there was a bug with autovacuum in 8.1.x? Is autovacuum under 8.1.9 safe or should I wait until I upgrade? Thanks in advance. -- irene --------------------------------------------------------------------- Irene Barg Email: ibarg@noao.edu NOAO/AURA Inc. http://www.noao.edu/noao/staff/ibarg 950 N. Cherry Ave. Voice: 520-318-8273 Tucson, AZ 85726 USA FAX: 520-318-8360 ---------------------------------------------------------------------
On 12/04/2009 17:27, Irene Barg wrote: > We are running postgresql-8.1.9 and plan to upgrade to 8.2 or even 8.3 > but can't just yet. I need to run analyze periodically (like hourly), Well, the current version in that branch is 8.1.17, so you're missing a *lot* of bug fixes. It would be worth your while looking through the release notes for the intervening 8.1.X releases - you may well find the answer to your question there. Ray. ------------------------------------------------------------------ Raymond O'Donnell, Director of Music, Galway Cathedral, Ireland rod@iol.ie Galway Cathedral Recitals: http://www.galwaycathedral.org/recitals ------------------------------------------------------------------
On Sun, 2009-04-12 at 09:27 -0700, Irene Barg wrote: > Hi, > > We are running postgresql-8.1.9 and plan to upgrade to 8.2 or even 8.3 > but can't just yet. I need to run analyze periodically (like hourly), > but before I write a script to loop through the tables in each schema > and run analyze, I thought I would try autovacuum. I say one post that > said there was a bug with autovacuum in 8.1.x? > > Is autovacuum under 8.1.9 safe or should I wait until I upgrade? There was a serious issue in 8.1.4 that, in certain situations, would make VACUUM and AUTOVACUUM totally inefective. But, afaik, it's fixed since 8.1.6. joao > Thanks in advance. > -- irene > --------------------------------------------------------------------- > Irene Barg Email: ibarg@noao.edu > NOAO/AURA Inc. http://www.noao.edu/noao/staff/ibarg > 950 N. Cherry Ave. Voice: 520-318-8273 > Tucson, AZ 85726 USA FAX: 520-318-8360 > --------------------------------------------------------------------- >
"Raymond O'Donnell" <rod@iol.ie> writes: > On 12/04/2009 17:27, Irene Barg wrote: >> We are running postgresql-8.1.9 and plan to upgrade to 8.2 or even 8.3 >> but can't just yet. I need to run analyze periodically (like hourly), > Well, the current version in that branch is 8.1.17, so you're missing a > *lot* of bug fixes. It would be worth your while looking through the > release notes for the intervening 8.1.X releases - you may well find the > answer to your question there. Like, say, here: http://www.postgresql.org/docs/8.1/static/release-8-1-16.html regards, tom lane
Hi, I found the answer i needed in the HISTORY file that came with the source as well as the online release notes below. I found the answer to a few other questions as well. I will do more digging before posting in the future. Thank you all. --irene Tom Lane wrote: > "Raymond O'Donnell" <rod@iol.ie> writes: >> On 12/04/2009 17:27, Irene Barg wrote: >>> We are running postgresql-8.1.9 and plan to upgrade to 8.2 or even 8.3 >>> but can't just yet. I need to run analyze periodically (like hourly), > >> Well, the current version in that branch is 8.1.17, so you're missing a >> *lot* of bug fixes. It would be worth your while looking through the >> release notes for the intervening 8.1.X releases - you may well find the >> answer to your question there. > > Like, say, here: > http://www.postgresql.org/docs/8.1/static/release-8-1-16.html > > regards, tom lane -- --------------------------------------------------------------------- Irene Barg Email: ibarg@noao.edu NOAO/AURA Inc. http://www.noao.edu/noao/staff/ibarg 950 N. Cherry Ave. Voice: 520-318-8273 Tucson, AZ 85726 USA FAX: 520-318-8360 ---------------------------------------------------------------------
Good Afternoon Irene
Please keep us apprised on how your implementation progresses..
Ta Me Go Maith
Martin
______________________________________________
Disclaimer and Confidentiality/Verzicht und Vertraulichkeitanmerkung / Note de déni et de confidentialité
> Date: Sun, 12 Apr 2009 15:28:57 -0700
> From: ibarg@noao.edu
> To: tgl@sss.pgh.pa.us
> CC: rod@iol.ie; pgsql-general@postgresql.org
> Subject: Re: [GENERAL] psql 8.1.9 autovacuum safe?
>
> Hi,
>
> I found the answer i needed in the HISTORY file that came with the
> source as well as the online release notes below. I found the answer to
> a few other questions as well. I will do more digging before posting in
> the future.
>
> Thank you all.
> --irene
>
> Tom Lane wrote:
> > "Raymond O'Donnell" <rod@iol.ie> writes:
> >> On 12/04/2009 17:27, Irene Barg wrote:
> >>> We are running postgresql-8.1.9 and plan to upgrade to 8.2 or even 8.3
> >>> but can't just yet. I need to run analyze periodically (like hourly),
> >
> >> Well, the current version in that branch is 8.1.17, so you're missing a
> >> *lot* of bug fixes. It would be worth your while looking through the
> >> release notes for the intervening 8.1.X releases - you may well find the
> >> answer to your question there.
> >
> > Like, say, here:
> > http://www.postgresql.org/docs/8.1/static/release-8-1-16.html
> >
> > regards, tom lane
>
> --
> ---------------------------------------------------------------------
> Irene Barg Email: ibarg@noao.edu
> NOAO/AURA Inc. http://www.noao.edu/noao/staff/ibarg
> 950 N. Cherry Ave. Voice: 520-318-8273
> Tucson, AZ 85726 USA FAX: 520-318-8360
> ---------------------------------------------------------------------
>
> --
> Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
Windows Live™: Keep your life in sync. Check it out.
Please keep us apprised on how your implementation progresses..
Ta Me Go Maith
Martin
______________________________________________
Disclaimer and Confidentiality/Verzicht und Vertraulichkeitanmerkung / Note de déni et de confidentialité
This message is confidential. If you should not be the intended receiver, then we ask politely to report. Each unauthorized forwarding or manufacturing of a copy is inadmissible. This message serves only for the exchange of information and has no legal binding effect. Due to the easy manipulation of emails we cannot take responsibility over the the contents.
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni.
> Date: Sun, 12 Apr 2009 15:28:57 -0700
> From: ibarg@noao.edu
> To: tgl@sss.pgh.pa.us
> CC: rod@iol.ie; pgsql-general@postgresql.org
> Subject: Re: [GENERAL] psql 8.1.9 autovacuum safe?
>
> Hi,
>
> I found the answer i needed in the HISTORY file that came with the
> source as well as the online release notes below. I found the answer to
> a few other questions as well. I will do more digging before posting in
> the future.
>
> Thank you all.
> --irene
>
> Tom Lane wrote:
> > "Raymond O'Donnell" <rod@iol.ie> writes:
> >> On 12/04/2009 17:27, Irene Barg wrote:
> >>> We are running postgresql-8.1.9 and plan to upgrade to 8.2 or even 8.3
> >>> but can't just yet. I need to run analyze periodically (like hourly),
> >
> >> Well, the current version in that branch is 8.1.17, so you're missing a
> >> *lot* of bug fixes. It would be worth your while looking through the
> >> release notes for the intervening 8.1.X releases - you may well find the
> >> answer to your question there.
> >
> > Like, say, here:
> > http://www.postgresql.org/docs/8.1/static/release-8-1-16.html
> >
> > regards, tom lane
>
> --
> ---------------------------------------------------------------------
> Irene Barg Email: ibarg@noao.edu
> NOAO/AURA Inc. http://www.noao.edu/noao/staff/ibarg
> 950 N. Cherry Ave. Voice: 520-318-8273
> Tucson, AZ 85726 USA FAX: 520-318-8360
> ---------------------------------------------------------------------
>
> --
> Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
Windows Live™: Keep your life in sync. Check it out.
On Sun, Apr 12, 2009 at 4:28 PM, Irene Barg <ibarg@noao.edu> wrote: > Hi, > > I found the answer i needed in the HISTORY file that came with the source as > well as the online release notes below. I found the answer to a few other > questions as well. I will do more digging before posting in the future. Funny thing is, the more you dig, the more questions you'll have. They'll just be that much more detailed.