On Wed, Jul 11, 2012 at 4:46 AM, Andy Halsall wrote:
> Version.
> PostgreSQL 9.1.2 on x86_64-unknown-linux-gnu, compiled by gcc (GCC) 4.5.2,
> 64-bit
>
> Server.
> Server: RX800 S2 (8 x Xeon 7040 3GHz dual-core processors, 32GB memory
> O/S: SLES11 SP1 64-bit
I don't really know how to co
On 07/17/2012 11:33 PM, Andy Halsall wrote:
If you're working with ISAM-like access though, cursors may well be
very helpful for you. It's a pity for your app that Pg doesn't support
cursors that see changes committed after cursor creation, since these
are ideal when emulating ISAM "next re
On 07/16/2012 06:13 PM, Andy Halsall wrote:
Thanks for the responses. I take the points - the times we're dealing
with are very small. Sorry but I'm a bit confused by the suggestions
around function types / prepared statements, but probably haven't been
clear in my question: I'm invoking a PL/P
On 07/11/2012 07:46 PM, Andy Halsall wrote:
I've written an Immutable stored procedure that takes no parameters
and returns a fixed value to try and determine the round trip overhead
of a query to PostgreSQL. Call to sp is made using libpq. We're all
local and using UNIX domain sockets.
PL/
Andy Halsall writes:
> I've written an Immutable stored procedure that takes no parameters and
> returns a fixed value to try and determine the round trip overhead of a query
> to PostgreSQL. Call to sp is made using libpq. We're all local and using UNIX
> domain sockets.
> Client measures ar