Sender: root@sunpine.krs.ru
Message-ID: <37F083E2.5C40D897@krs.ru>
Date: Tue, 28 Sep 1999 17:01:22 +0800
From: Vadim Mikheev <vadim@krs.ru>
Organization: OJSC Rostelecom (Krasnoyarsk)
MIME-Version: 1.0
To: "Ansley, Michael" <Michael.Ansley@intec.co.za>
CC: "'pgsql-interfaces@postgresql.org'" <pgsql-interfaces@postgreSQL.org>,
	"'pgsql-hackers@postgresql.org'" <pgsql-hackers@postgreSQL.org>
Subject: Re: [HACKERS] Latest tree
References: <1BF7C7482189D211B03F00805F8527F748C0D0@S-NATH-EXCH2>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

"Ansley, Michael" wrote:
> 
> Hi, all,
> 
> Whoever is doing the SSL stuff:
> In postmaster.c, at lines 995, and 1841, there is code that is not wrapped
> in the USE_SSL define.
> 
> Last night I checked out the latest source, and couldn't get it to compile.
> It seems that the function heap_openr() has a new parameter, and there are
> calls that have not been updated yet.  I was a little hesitant to go adding
> stuff, as the new parameter is a LOCKTYPE, and I wouldn't know what locks
> are required where, so I just left well alone.  Any comments on this?  There
> is another function which is paired up with it, but I forget the name, which
> also has a new parameter, it seems, and also has calls which have not yet
> been updated.

I fixed all this yesterday while committing my WAL changes...

Vadim