Skip site navigation (1) Skip section navigation (2)

Re: fix for pg_upgrade

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: panam <panam(at)gmx(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: fix for pg_upgrade
Date: 2011-09-28 23:14:51
Message-ID: 201109282314.p8SNEp506547@momjian.us (view raw or flat)
Thread:
Lists: pgsql-hackers
panam wrote:
> Hi Bruce,
> 
> here is the file you asked for: 
> http://postgresql.1045698.n5.nabble.com/file/n4850735/pg_upgrade_logfile.txt
> pg_upgrade_logfile.txt 
> 

OK, I see it using -b to pg_ctl:

	""C:\Program Files\PostgreSQL\9.1\bin/pg_ctl" -w -l "nul" -D "D:\applications\postgres\9.1" -o "-p 5432 -b" start >> "nul" 2>&1"

What I have to find out is whether this is passed to the individual
session processes.  I guess is no.

> I guess you are not addressing me here, right?
> > The server will need to 
> > be started with -b and this will disable autovacuum.  Can someone on 
> > Windows try this?

No, not really.  I think it is a software bug and I need guidance about
a solution.

-- 
  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

pgsql-hackers by date

Next:From: Jaime CasanovaDate: 2011-09-28 23:55:31
Subject: Re: Updated version of pg_receivexlog
Previous:From: Daniel FarinaDate: 2011-09-28 22:18:20
Subject: Re: feature request: auto savepoint for interactive psql when in transaction.

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group