on 1/29/06 8:00 PM, mike@xxxxxxxx purportedly said: > On Sun, Jan 29, 2006 at 06:03:41PM +0100, Joachim Wieland wrote: >> On Sat, Jan 28, 2006 at 08:26:01PM +0100, Alexander Farber wrote: >>> Could you explain a bit more, where to get the OIDs? >> >> They are in the pg_type table, it is described here: >> >> http://www.postgresql.org/docs/8.1/static/catalog-pg-type.html > > For standard types you could include server/catalog/pg_type.h and > use TEXTOID, INT4OID, etc. But as Tom Lane mentioned, if the query > is written so the backend can infer the types then you don't need > to bother. This thread has particular interest to me as well--the libpq documentation and examples seem to imply that the backend will consider all parameters to be string literals, although postgres is smart enough to perform conversions. However, there was an issue (perhaps no longer in 8.x) that in cases of implicit conversions the planner would have the tendency to perform sequential searches when otherwise (i.e. when the type is more explicit) it would do an index search. My question, then: is this still the case and if so, is there another way to inform the planner of the type such as explicit type casts? I guess I am wondering more specifically what "if the query is written so the backend can infer the types" means. Thanks, Keary Suska Esoteritech, Inc. "Demystifying technology for your home or business"
