Re: Apache2 PostgreSQL http authentication

From: Tino Wildenhain <tino(at)wildenhain(dot)de>
To: Magnus Hagander <magnus(at)hagander(dot)net>
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:09:48
Message-ID: 470A645C.1080405@wildenhain.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

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.

Regards
Tino

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Magnus Hagander 2007-10-08 17:12:23 Re: Apache2 PostgreSQL http authentication
Previous Message Josh Tolley 2007-10-08 13:43:42 Re: postgresql on NFS.. recommended? not recommended?