From: Magnus Hagander <magnus@hagander.net>
To: Tino Wildenhain <tino@wildenhain.de>
Cc: Jeff@PointHere.net, "'D'Arcy J.M. Cain'" <darcy@druid.net>
Cc: pgsql-performance@postgresql.org
Subject: Re: Apache2 PostgreSQL http authentication
Date: Mon, 08 Oct 2007 19:12:23 +0200
Message-ID: <470A64F7.2090106@hagander.net> (raw)
In-Reply-To: <470A645C.1080405@wildenhain.de>
References: <200710080812110000@463712056>
<470A645C.1080405@wildenhain.de>
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
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: magnus@hagander.net, tino@wildenhain.de, darcy@druid.net
Subject: Re: Apache2 PostgreSQL http authentication
In-Reply-To: <470A64F7.2090106@hagander.net>
* 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