From: Tom Lane <tgl@sss.pgh.pa.us>
To: Mark Crosland <mark.crosland@gmail.com>
cc: pgsql-interfaces@postgresql.org
Subject: Re: Traversing the catalog using heap_open, systable_beginscan, ...
In-reply-to: 
 <CAJjS_dPv2JerM5d=yfDHif0M+VHRcsNwFuvRtLEDmGWpp-OGpA@mail.gmail.com>
References: 
 <CAJjS_dOXaAkKRoso1J3ShQXoBmA=SFxtiN9vNqGHq9fn4bbYhw@mail.gmail.com>
 <31976.1384013537@sss.pgh.pa.us>
 <CAJjS_dPv2JerM5d=yfDHif0M+VHRcsNwFuvRtLEDmGWpp-OGpA@mail.gmail.com>
Comments: In-reply-to Mark Crosland <mark.crosland@gmail.com>
 message dated "Mon, 11 Nov 2013 14:01:00 -0800"
Date: Mon, 11 Nov 2013 21:03:14 -0500
Message-ID: <20630.1384221794@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-interfaces-owner@postgresql.org

Mark Crosland <mark.crosland@gmail.com> writes:
> Thanks, that helps. I can get table and column info from the catalog now.
> What is the recommended way (structs to access via one of the scan/modify
> callbacks?) to retrieve the column, operation and value, "col", "=" and
> "val" in this example. And is the same method used for both queries and
> updates?
> select * from table where col=val

contrib/postgres_fdw might be a useful example for you.  A lot of this
stuff isn't documented terribly well, you just have to look for some
example code that does what you want to do.

			regards, tom lane


-- 
Sent via pgsql-interfaces mailing list (pgsql-interfaces@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-interfaces