Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 9037964FCCF for ; Fri, 19 Sep 2008 17:14:25 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 35687-08 for ; Fri, 19 Sep 2008 17:14:21 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id AA3EE64FCC7 for ; Fri, 19 Sep 2008 17:14:21 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id m8JKEGFf025234; Fri, 19 Sep 2008 16:14:17 -0400 (EDT) To: "Merlin Moncure" cc: "Andrew Chernow" , "Alvaro Herrera" , PostgreSQL-development Subject: Re: [PATCHES] libpq events patch (with sgml docs) In-reply-to: References: <48C18533.2000204@esilo.com> <454.1221626213@sss.pgh.pa.us> <48D0DFBE.9050900@esilo.com> <8872.1221653812@sss.pgh.pa.us> <48D1041D.5070808@esilo.com> <10839.1221658586@sss.pgh.pa.us> <48D11443.4010608@esilo.com> <48D11631.8070709@esilo.com> <28666.1221840662@sss.pgh.pa.us> <48D3EBEC.1040503@esilo.com> Comments: In-reply-to "Merlin Moncure" message dated "Fri, 19 Sep 2008 14:39:27 -0400" Date: Fri, 19 Sep 2008 16:14:16 -0400 Message-ID: <25233.1221855256@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200809/1270 X-Sequence-Number: 124399 "Merlin Moncure" writes: > On Fri, Sep 19, 2008 at 2:14 PM, Andrew Chernow wrote: >> BTW, the event system might be an alternative solution for PGNoticeHooks >> (PGEVT_NOTICE). > Another possible use of the event hooks -- just spitballing here -- is > to generate an event when a notification comes through (you would > still receive events the old way., by command or PQconsumeInput). Seems rather pointless; you'd just be adding multiple ways to do things we can do perfectly well now. > Maybe this would eventually replace the current notification interface > (wasn't this going to be changed anyways?) No, I don't think anyone was unhappy with the libpq API for it. regards, tom lane