pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Cristóvão Dalla Costa <cbraga@bsi.com.br>
Cc: pgsql-general@postgresql.org
Cc: pgsql-interfaces@postgresql.org
Subject: Re: LISTEN/NOTIFY
Date: Fri, 04 Oct 2002 22:54:02 -0400
Message-ID: <264.1033786442@sss.pgh.pa.us> (raw)
In-Reply-To: <3D9DFEF3.6020509@bsi.com.br>
References: <3D9DFEF3.6020509@bsi.com.br>

=?ISO-8859-1?Q?Crist=F3v=E3o_Dalla_Costa?= <cbraga@bsi.com.br> writes:
> I'm developing an e-commerce site using Apache/mod_perl and, for 
> performance, I intend to cache rows such as user and product information 
> inside Perl. I think the LISTEN/NOTIFY interface would be perfect for 
> invalidating the cache when a product/user gets updated, yet I have not 
> found a way to access it from Perl -- DBI, or DBD::Pg even, offer no way 
> to "listen".

I don't know what the DBI/DBD design philosophy is regarding
database-specific extensions --- but it would seem reasonable to me
for DBD::Pg to offer some way to get at LISTEN functionality.  Can
anyone suggest how to do this in the context of DBI?

I suggest moving any followups to pgsql-interfaces, where this
discussion would be more on-topic.

			regards, tom lane



view thread (5+ messages)  latest in thread

Message-ID: <264.1033786442@sss.pgh.pa.us>
Permalink:  ../264.1033786442@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/264.1033786442@sss.pgh.pa.us

 · 

reply

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-interfaces@postgresql.org
  Cc: tgl@sss.pgh.pa.us, cbraga@bsi.com.br, pgsql-general@postgresql.org
  Subject: Re: LISTEN/NOTIFY
  In-Reply-To: <264.1033786442@sss.pgh.pa.us>

* 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