X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 64AB19DD738 for ; Fri, 13 Jan 2006 16:10:37 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 78666-10-2 for ; Fri, 13 Jan 2006 16:10:31 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from vms040pub.verizon.net (vms040pub.verizon.net [206.46.252.40]) by postgresql.org (Postfix) with ESMTP id 69F9E9DD732 for ; Fri, 13 Jan 2006 16:10:27 -0400 (AST) Received: from osgiliath.mathom.us ([70.108.47.21]) by vms040.mailsrvcs.net (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) with ESMTPA id <0IT10085HS11QDO4@vms040.mailsrvcs.net> for pgsql-performance@postgresql.org; Fri, 13 Jan 2006 14:10:14 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by osgiliath.mathom.us (Postfix) with ESMTP id 987CD6061604 for ; Fri, 13 Jan 2006 15:10:12 -0500 (EST) Received: from osgiliath.mathom.us ([127.0.0.1]) by localhost (osgiliath.home.mathom.us [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 13563-02-2 for ; Fri, 13 Jan 2006 15:10:11 -0500 (EST) Received: by osgiliath.mathom.us (Postfix, from userid 1000) id E58BC6061601; Fri, 13 Jan 2006 15:10:11 -0500 (EST) Date: Fri, 13 Jan 2006 15:10:11 -0500 From: Michael Stone Subject: insert without oids To: pgsql-performance@postgresql.org Mail-followup-to: pgsql-performance@postgresql.org Message-id: <20060113201011.GI1408@mathom.us> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii; format=flowed Content-disposition: inline X-Pgp-Fingerprint: 53 FF 38 00 E7 DD 0A 9C 84 52 84 C5 EE DF 7C 88 X-Virus-Scanned: Debian amavisd-new at mathom.us User-Agent: Mutt/1.5.11 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.103 required=5 tests=[AWL=0.103] X-Spam-Score: 0.103 X-Spam-Level: X-Archive-Number: 200601/166 X-Sequence-Number: 16644 OIDs seem to be on their way out, and most of the time you can get a more helpful result by using a serial primary key anyway, but I wonder if there's any extension to INSERT to help identify what unique id a newly-inserted key will get? Using OIDs the insert would return the OID of the inserted row, which could be useful if you then want to refer to that row in a subsequent operation. You could get the same result by manually retrieving the next number in the sequence and using that value in the insert, but at the cost of additional DB operations. Are there plans on updating the insert API for the post-OID world? Mike Stone