Lua is an efficient and easy to learn scripting language that has been designed to be be embedded into other software. It is being used as an extension language in many proprietary and open source products. Lua programs are internally compiled to a bytecode which is then executed by a very fast "virtual machine". Lua offers a very easy to use interface to software written in C, which allows the creation of extension modules, or bindings to other pieces of software, using the C language.
The core of our products is written in C and PostgreSQL is the database of choice. Most extensions to the software, and more recently complete applications, are written in the Lua language. These extensions or applications access internal state of the C core using Lua bindings. While we used Lua to access PostgreSQL since many years already, the Lua interface to PostgreSQL was relatively simple and offered only a subset of libpq's functionality. In preparation of a talk for PGConf.EU 2012, I decided some time ago to make the Lua PostgreSQL binding functionally equivalent to libpq. The old interface lacked a lot of support functions, asynchronous connection and command execution, support for asynchronous notifications etc.
Over the last weeks (or maybe months) I continously extended the Lua PostgreSQL interface, which can be found at https://github.com/mbalmer/luapgsql. The function names are more or less the same as in libpq, minus the PQ prefix. And the C structs PGconn, PGresult etc. are wrapped as Lua "objects" and can use the Lua object syntax object:method():
conn = pgsql.connectdb('dbname=test')
if conn:status() ~= pgsql.CONNECTION_OK then
res = conn:exec('select * from mydata')
for n = 1, res:ntuples() do
Besides the pgsql.connectb() function there is also support for asynchronous connection. And for queries prepared statements can be used as well; all queries can either be executed asynchronous or synchronous.
I apologize that there is no proper english documentation yet, for now you will have to look at luapgsql.c, towards the end of the file, for a list of all functions provided. I hope to have proper documentation ready later this year.