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

Re: pg_resetxlog as root

From: Neil Conway <neilc(at)samurai(dot)com>
To: Dave Page <dpage(at)vale-housing(dot)co(dot)uk>
Cc: pgsql-patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: pg_resetxlog as root
Date: 2004-12-14 01:59:16
Message-ID: 1102989556.28882.8.camel@localhost.localdomain (view raw or flat)
Thread:
Lists: pgsql-patches
On Mon, 2004-12-13 at 11:30 +0000, Dave Page wrote:
>  
> > -----Original Message-----
> > From: Neil Conway [mailto:neilc(at)samurai(dot)com] 
> > Sent: 13 December 2004 03:59
> > To: Dave Page
> > Cc: pgsql-patches
> > Subject: RE: [PATCHES] pg_resetxlog as root
> > 
> > On Sun, 2004-12-12 at 23:59 +0000, Dave Page wrote:
> > > Sounds reasonable to me.
> > 
> > Attached is a patch that implements this.
> > src/port/backend/win32/security.c is moved to 
> > src/port/win32_security.c, and conditionally added to 
> > LIBOBJS. Note that I don't have much experience with the 
> > build system, and less still with the Win32 port, so please 
> > let me know if there's a better way to do this. Also, I don't 
> > have a Windows build environment -- could someone verify 
> > whether this builds on Win32?
> 
> Not quite there I'm afraid. Unfortunately I don't have time right now to
> look further, but I don't suppose it's a major problem [...]

On closer inspection, there are other places where Win32 could make this
check but does not (e.g. pg_ctl, initdb). Therefore I've decided not to
fix the Win32 side of things, and just committed the patch as is. IMHO
it would be wise for the Win32 folks to fix this, but I'll leave that
decision to them (... without a Win32 build environment I'm not really
comfortable committing fixes during RC without being able to compile,
much less test them).

-Neil



In response to

pgsql-patches by date

Next:From: Neil ConwayDate: 2004-12-14 03:39:49
Subject: Re: dropdb/contrib-regression
Previous:From: Andrew DunstanDate: 2004-12-14 01:44:53
Subject: Re: [HACKERS] dropdb/contrib-regression

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