Message-ID: <470A64F7.2090106@hagander.net>
Date: Mon, 08 Oct 2007 19:12:23 +0200
From: Magnus Hagander <magnus@hagander.net>
User-Agent: Thunderbird 2.0.0.6 (X11/20070728)
MIME-Version: 1.0
To: Tino Wildenhain <tino@wildenhain.de>
CC: Jeff@PointHere.net, "'D'Arcy J.M. Cain'" <darcy@druid.net>,
	pgsql-performance@postgresql.org
Subject: Re: Apache2 PostgreSQL http authentication
References: <200710080812110000@463712056> <470A645C.1080405@wildenhain.de>
In-Reply-To: <470A645C.1080405@wildenhain.de>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Tino Wildenhain wrote:
> Magnus Hagander schrieb:
>> I'd consider having a small daemon LISTENing for NOTIFYs that you send
>> by triggers whenever the table has changed. That'll make sure it only
>> dumps if something actually changed. And you can also implement some
>> ratelimiting if needed.
> Do you really think such a homegrown solution will be more
> performant then just accessing postgres? If you have
> many users the lookup time in a .htaccess/.htpasswd is not for
> free either.

Right, that's what it depends on. I'd measure it. In systems with not
too many users (say just a couple of thousand), I've measured great
improvements in speed. It depends on how you authenticate as well - if
you authenticate every single http request, the difference is greater.

//Magnus