X-Original-To: pgsql-php-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 3942453597 for ; Wed, 23 Mar 2005 14:53:22 +0000 (GMT) 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 02732-09 for ; Wed, 23 Mar 2005 14:53:14 +0000 (GMT) Received: from floppy.pyrenet.fr (unknown [194.116.145.2]) by svr1.postgresql.org (Postfix) with ESMTP id 251DE52A05 for ; Wed, 23 Mar 2005 14:53:03 +0000 (GMT) Received: by floppy.pyrenet.fr (Postfix, from userid 106) id 6B8F430EA1; Wed, 23 Mar 2005 15:53:03 +0100 (MET) From: Christopher Browne X-Newsgroups: pgsql.interfaces.php Subject: Re: Delay INSERT Date: Wed, 23 Mar 2005 09:42:18 -0500 Organization: cbbrowne Computing Inc Lines: 24 Message-ID: References: <20050321131047.93504.qmail@web53406.mail.yahoo.com> <20050321161555.GA22145@winnie.fuhr.org> <16718190640.20050323144638@on.kg> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@news.hub.org X-message-flag: Outlook is rather hackable, isn't it? X-Home-Page: http://www.cbbrowne.com/info/ X-Affero: http://svcs.affero.net/rm.php?r=cbbrowne User-Agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.4 (Jumbo Shrimp, linux) Cancel-Lock: sha1:B6zB7wVatWfmkE4F25D/inBNN1s= To: pgsql-php@postgresql.org X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.389 tagged_above=0 required=5 tests=AWL, INFO_TLD X-Spam-Level: X-Archive-Number: 200503/58 X-Sequence-Number: 3073 After a long battle with technology, skyer@on.kg ("ON.KG"), an earthling, wrote: > Does PostgreSQL have something like "INSERT DELAYD" - like it is used in > MySQL? > > or any other way to delay inserting? What problem are you trying to solve by using "INSERT DELAYED"? As far as I can tell, the problem solved using "INSERT DELAYED" is that in MySQL AB's product, processes take out full table locks when they modify tables. That is completely irrelevant with PostgreSQL, as PostgreSQL does not lock tables that way. Unless your concern is something rather more abstruse, I think you're trying to solve a problem that simply doesn't exist. There is no reason to delay inserts in PostgreSQL because there are no such locks. -- (format nil "~S@~S" "cbbrowne" "gmail.com") http://linuxdatabases.info/info/slony.html "I would rather spend 10 hours reading someone else's source code than 10 minutes listening to Musak waiting for technical support which isn't." -- Dr. Greg Wettstein, Roger Maris Cancer Center