Bruce Momjian <[EMAIL PROTECTED]> writes:Tom Lane wrote:Are those exposed through the libpq interface?
No, because libpq doesn't really have any concept of prepared statements. It would probably make sense to add some more API to libpq to allow creation and interrogation of prepared statements, but no one's got around to that yet.
Uh, if libpq doesn't know about it, how is that information accessed?
That's exactly the problem...
Currently the only way to do that would be to have a user defined function that calls SPI_prepare() with the query string and returns the desired information to the client.
Jan
-- #======================================================================# # It's easier to get forgiveness for being wrong than for being right. # # Let's break this rule - forgive me. # #================================================== [EMAIL PROTECTED] #
---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
