From: Jeffrey Brower <Jeff@PointHere.net>
To: 'D'Arcy J.M. Cain' <darcy@druid.net>
Cc: pgsql-performance@postgresql.org
Subject: Re: Apache2 PostgreSQL http authentication
Date: Sun, 7 Oct 2007 16:58:29 -0400
Message-ID: <519f01c80924$cfed09b0$1602a8c0@warpcore> (raw)
In-Reply-To: <20071007164457.81f59d1d.darcy@druid.net>
References: <501201c808e4$06e0a350$1602a8c0@warpcore>
<20071007164457.81f59d1d.darcy@druid.net>
Using a cron task was my first thought. Unfortunately, new users are given
a logon that they immediately use. I thought about shelling out and
updating a password file on an on-demand basis but I am not sure if that is
such a great idea either - especially since users can change their passwords
and renew their logons at will as well.
Jeff
-----Original Message-----
From: D'Arcy J.M. Cain [mailto:darcy@druid.net]
Sent: Sunday, October 07, 2007 4:45 PM
To: Jeff@PointHere.net
Cc: pgsql-performance@postgresql.org
Subject: Re: [PERFORM] Apache2 PostgreSQL http authentication
On Sun, 7 Oct 2007 09:14:43 -0400
"Jeffrey Brower" <Jeff@PointHere.net> wrote:
> As I say, from a performance point of view, I would really like to
> know if there is anything I can do to make sure that postgres is
> performing as quickly as possible under apache2 so that my http
> authentication is not impacted too significantly.
How often does the user information change? Can you simply create standard
Apache password files from cron during non-busy hours?
Sometimes the lower tech solution works best.
--
D'Arcy J.M. Cain <darcy@druid.net> | Democracy is three wolves
http://www.druid.net/darcy/ | and a sheep voting on
+1 416 425 1212 (DoD#0082) (eNTP) | what's for dinner.
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: pgsql-performance@postgresql.org
Cc: Jeff@PointHere.net, darcy@druid.net
Subject: Re: Apache2 PostgreSQL http authentication
In-Reply-To: <519f01c80924$cfed09b0$1602a8c0@warpcore>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox