Re: Patch for pg_upgrade to turn off autovacuum

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Jeff Davis <pgsql(at)j-davis(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Patch for pg_upgrade to turn off autovacuum
Date: 2011-04-21 22:22:42
Message-ID: 201104212222.p3LMMg117746@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > Tom Lane wrote:
> >> Huh? Why would that be? Seems like you've done something in the wrong
> >> place if that's an issue.
>
> > Yeah, it is complicated. I don't really care if autovacuum runs on the
> > old cluster (we only move the files while the server is down). We only
> > want autovacuum not to mess with the relfrozenxids we set on the new
> > cluster while the table file is empty.
>
> > The other issue is that the old alpha binary will not know about the -b
> > flag and hence will not start.
>
> Well, once again, why are you trying to do that? It's not the source
> postmaster that needs this flag.

Well, consider that this also locks out non-super users so I figured it
would be good to run the old and new in the same binary upgrade mode.
Again, we can do just the new cluster for 9.1. I can also control the
behavior based on the catalog version number, which seems the most
logical.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Davis 2011-04-21 22:34:46 Re: Patch for pg_upgrade to turn off autovacuum
Previous Message Tom Lane 2011-04-21 22:10:03 Re: Patch for pg_upgrade to turn off autovacuum