Re: LISTEN filtering

From: Merlin Moncure <mmoncure(at)gmail(dot)com>
To: Greg Sabino Mullane <greg(at)turnstep(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: LISTEN filtering
Date: 2011-06-21 18:45:25
Message-ID: BANLkTimRDKjBNsova_eFo=fe4AXic03yNQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, Jun 21, 2011 at 10:58 AM, Greg Sabino Mullane <greg(at)turnstep(dot)com> wrote:
> Quick idea to toss out there: allowing an option to LISTEN to
> only 'hear' from superusers (or self). I've got an app that uses a lot
> of listen/notify to talk to other subprocesses. However, it
> would be nice if non-superusers could not affect the behavior
> of this application: right now, anyone can issue a NOTIFY. (Yes,
> I can look information up about the calling notifier's PID,
> but that's not easy). Rather than a full 'rights' system (which
> would be complex overkill), what if we had an  option to LISTEN
> that said "I only want to hear notices coming from superusers"?
> Or perhaps an option that says "I only want to hear notices
> coming from me (same role)"? This would not affect notifications
> at all, but would simply act as a quick filter on incoming
> notices for a specific listener.

hm. maybe you could use the 9.1 payload feature so that your custom
behavior would only be invoked if a particular payload was sent?

merlin

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Sylvain Rabot 2011-06-21 19:37:12 Re: Partitioning and constraint exclusion
Previous Message Cédric Villemain 2011-06-21 17:00:30 Re: PostgreSQL 8.4.8 bringing my website down every evening