Re: Conditional NOTIFY is not implemented

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: tomas(at)fabula(dot)de
Cc: pgsql-hackers(at)postgreSQL(dot)org, pgsql-bugs(at)postgreSQL(dot)org, matthew(dot)copeland(at)honeywell(dot)com
Subject: Re: Conditional NOTIFY is not implemented
Date: 2001-09-07 04:30:44
Message-ID: 21265.999837044@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

tomas(at)fabula(dot)de writes:
> My pattern of use for ``CREATE RULE... NOTIFY...'' was, up to now, to get
> a notice when anything changed on a table and then go look what happened;
> a `poor man's statement level trigger' if you wish. Thus, the old behavior
> didn't bother me that much. I don't know how others are using it.

Yeah, that is the normal and recommended usage pattern for NOTIFY, so
getting a NOTIFY when nothing actually happened is fairly harmless.
(Undoubtedly that's why no one complained before.)

Changing the rewriter to error out when it couldn't really Do The Right
Thing seemed like a good idea at the time, but now it seems clear that
this didn't do anything to enhance the usefulness of the system. Unless
someone objects, I'll change it back for 7.2.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Larry Rosenman 2001-09-07 04:37:53 Re: [COMMITTERS] pgsql/src/backend/utils/mb encnames.c win1251. ...
Previous Message tomas 2001-09-07 04:10:01 Re: Conditional NOTIFY is not implemented

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2001-09-07 04:32:33 Beta Monday?
Previous Message Bruce Momjian 2001-09-07 04:30:24 Re: [HACKERS] JDBC pg_description update needed for CVS tip