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@xxxxxxxxx] Sent: Sunday, October 07, 2007 4:45 PM To: Jeff@xxxxxxxxxxxxx Cc: pgsql-performance@xxxxxxxxxxxxxx Subject: Re: Apache2 PostgreSQL http authentication On Sun, 7 Oct 2007 09:14:43 -0400 "Jeffrey Brower" <Jeff@xxxxxxxxxxxxx> 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@xxxxxxxxx> | 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. ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings
