X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 550DA53611 for ; Fri, 8 Apr 2005 19:47:40 +0100 (BST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 08617-10 for ; Fri, 8 Apr 2005 18:47:37 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id E1392535EE for ; Fri, 8 Apr 2005 19:47:36 +0100 (BST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j38IlaGe016029; Fri, 8 Apr 2005 14:47:36 -0400 (EDT) To: Vivek Khera Cc: pgsql-sql@postgresql.org Subject: Re: Question on triggers and plpgsql In-reply-to: <986acdb4ff3bdac82c5e09c607bc7839@khera.org> References: <4255AA15.8000508@mochima.com> <14244.1112970986@sss.pgh.pa.us> <20050408145928.GA27718@phlogiston.dyndns.org> <986acdb4ff3bdac82c5e09c607bc7839@khera.org> Comments: In-reply-to Vivek Khera message dated "Fri, 08 Apr 2005 14:02:51 -0400" Date: Fri, 08 Apr 2005 14:47:36 -0400 Message-ID: <16028.1112986056@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.006 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200504/109 X-Sequence-Number: 21002 Vivek Khera writes: > I have a lot of processing that could benefit from this type of > synchronization, except the fact that there's no Pg command to "wait > until I get a notify message". This is a client library deficiency, not a problem with the backend or the protocol. In libpq it is actually possible to do it, but you have to select() or poll() on the socket for yourself, which is a tad ugly. OTOH, most apps that want to do that also want to wait on other sockets at the same time, so a cleaner-looking API wouldn't necessarily be any more useful. regards, tom lane