Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 533E647653D for ; Mon, 13 Jan 2003 17:16:10 -0500 (EST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 96C84476520 for ; Mon, 13 Jan 2003 17:16:09 -0500 (EST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.6/8.12.6) with ESMTP id h0DMGA5u006336; Mon, 13 Jan 2003 17:16:10 -0500 (EST) To: Ron Peterson Cc: pgsql-sql@postgresql.org Subject: Re: insert rule doesn't see id field In-reply-to: <20030113221129.GA32653@mtholyoke.edu> References: <20030107145422.GE12245@mtholyoke.edu> <13558.1041955268@sss.pgh.pa.us> <20030113221129.GA32653@mtholyoke.edu> Comments: In-reply-to Ron Peterson message dated "Mon, 13 Jan 2003 17:11:29 -0500" Date: Mon, 13 Jan 2003 17:16:09 -0500 Message-ID: <6335.1042496169@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200301/193 X-Sequence-Number: 11058 Ron Peterson writes: > I can find out this info > for the relation pulling the trigger easy enought, but how would I go > about getting this info when all I have is the table/field name? I > could create and execute a SQL query something like the following, but > is that really the way to get at this info in C code? Open the target relation and examine its tuple descriptor ... regards, tom lane