Hello Henning,

 

 

The database I’m using is on a VM hosted on the same physical server as the Kamailio server, so the network overhead is small.

That said, I’m not sure I would gain much with prepared statements… but a DBA audit suggested it would help.

 

Anyway… thanks for your input, and for confirming that sqlops cannot support prepared statements. :)

 

 

Regards,

Nicolas.

 

 

Hello,

 

the sqlops module only support “standard SQL” queries from the configuration. And practically speaking, if you are executing your query against a remote server, the network overhead will probably substancially higher than parsing the SQL statement on the server. So, I do not think there is actually a big benefit for using this.

 

If you need the last bit of performance, you could always implement a C module and implement it there. From my experience you will gain most with statement batching, especially for write operations.

 

Cheers,

 

Henning

 

 

 

Hello,

 

 

Trying again, in case this got unnoticed the first time.

I hope that by doing so I’m not breaching the rules of the mailing list.

 

If nobody answers, then I’ll conclude that nobody knows about that, and shall not insist anymore. :)

 

 

Regards,

Nicolas.

 

 

Hello,

 

 

I’m using sql_xquery from sqlops module to execute requests on a PostgreSQL database.

This work fine.

 

Now, for performance reasons, I would like to use prepared statements.

I’m wondering if this is possible using sql_xquery. I’ve looked at the code and documentation, it seems it is not supported.

Can you confirm ?

 

If not possible with sql_xquery, is it possible with another existing function ?

 

In the code, I’ve searched for « PQprepare » / « PQexecPrepared ».

These can be found only in « modules/db_postgres/pg_cmd.c », in function « pg_cmd_exec » which is exported from « modules/db_postgres/pg_mod.c » (see below).

I have no idea how to use these though… :/

 

Any ideas ?

 

 

 

/*

* Postgres module interface

*/

static cmd_export_t cmds[] = {

       {"db_ctx", (cmd_function)NULL, 0, 0, 0, 0},

       {"db_con", (cmd_function)pg_con, 0, 0, 0, 0},

       {"db_uri", (cmd_function)pg_uri, 0, 0, 0, 0},

       {"db_cmd", (cmd_function)pg_cmd, 0, 0, 0, 0},

       {"db_put", (cmd_function)pg_cmd_exec, 0, 0, 0, 0},

       {"db_del", (cmd_function)pg_cmd_exec, 0, 0, 0, 0},

       {"db_get", (cmd_function)pg_cmd_exec, 0, 0, 0, 0},

       {"db_upd", (cmd_function)pg_cmd_exec, 0, 0, 0, 0},

       {"db_sql", (cmd_function)pg_cmd_exec, 0, 0, 0, 0},

       {"db_res", (cmd_function)pg_res, 0, 0, 0, 0},

       {"db_fld", (cmd_function)pg_fld, 0, 0, 0, 0},

       {"db_first", (cmd_function)pg_cmd_first, 0, 0, 0, 0},

       {"db_next", (cmd_function)pg_cmd_next, 0, 0, 0, 0},

       {"db_setopt", (cmd_function)pg_setopt, 0, 0, 0, 0},

       {"db_getopt", (cmd_function)pg_getopt, 0, 0, 0, 0},

       {"db_bind_api", (cmd_function)db_postgres_bind_api, 0, 0, 0, 0},

       {0, 0, 0, 0, 0, 0}

};

 

 

 

Regards,

Nicolas.