Skip site navigation (1) Skip section navigation (2)

Re: Apache2 PostgreSQL http authentication

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Tino Wildenhain <tino(at)wildenhain(dot)de>
Cc: Jeff(at)PointHere(dot)net, "'D'Arcy J(dot)M(dot) Cain'" <darcy(at)druid(dot)net>, pgsql-performance(at)postgresql(dot)org
Subject: Re: Apache2 PostgreSQL http authentication
Date: 2007-10-08 17:12:23
Message-ID: 470A64F7.2090106@hagander.net (view raw or flat)
Thread:
Lists: pgsql-performance
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

In response to

pgsql-performance by date

Next:From: Campbell, LanceDate: 2007-10-09 14:11:43
Subject: SQL Monitoring
Previous:From: Tino WildenhainDate: 2007-10-08 17:09:48
Subject: Re: Apache2 PostgreSQL http authentication

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group