public inbox for [email protected]  

help / color / mirror / Atom feed

From: Marc G. Fournier <[email protected]>
To: Justin Clift <[email protected]>
Cc: [email protected]
Subject: Re: Inadequate hosting for www.postgresql.org
Date: Thu, 4 Nov 2004 00:55:11 -0400 (AST)
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <E7F85A1B5FF8D44C8A1AF6885BC9A0E4306FBC@ratbert.vale-housing.co.uk>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

On Thu, 4 Nov 2004, Justin Clift wrote:

> Marc G. Fournier wrote:
> <snip>
>> You might have hit it on the mark:
>
> Um, now I'm lost.  Recompiling the main PHP binary without 
> --enable-versioning was the winner?

Ya ... I think what happens is that when the main php starts up, the first 
thing it does is goes through its 'extensions' to make sure they are part 
of the same version ... *why* it would do it each and ever connection, vs 
just when apache starts up, I don't know ... but, I'm on a dial-up link at 
home and I can actually load wwwdevel.postgresql.org now, where before I 
had enough time to go to the kitchen for a drink waiting for it to load 
...

But, I also don't believe it was *just* that option ... the database was 
slow, due to the need for the vacuum full, which was apparent with the 
load times on the current site ...

But, after upgrading and restarting apache on all the VMs, with the change 
to PHP, even the servers loadavg are all back down to 'normal' ...

What I suspect is that before the PHP maintainer "split up" teh extensions 
to seperate ports each, instead of one built binary, he didn't have the 
versioning enabled ... it was only because of the splits that he added it, 
so it never affected us before ...

----
Marc G. Fournier           Hub.Org Networking Services (http://www.hub.org)
Email: [email protected]           Yahoo!: yscrappy              ICQ: 7615664

view thread (60+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: Inadequate hosting for www.postgresql.org
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox