[DOCS] pgbench acronym tps

I noticed that pgbench.sgml (or the manual elsewhere) does not explicitly mention what TPS stands for; I thought it might be useful to add. (reason I checked: someone on #postgresql took tps to mean 'tuples per second') Erik Rijkers pgbench.sgml.diff Description: Binary data -- Sent via pgsq

Re: [DOCS] Please provide stable target anchors

On Wed, Aug 4, 2010 at 3:03 PM, Daniele Varrazzo wrote: > I have prepared patches to add ids style 'libpq-pqconnectdb' to > varlistentry relative to libpq functions. This results in stable > anchors in html output. The ids have been generated using the script > available in

Re: [DOCS] Patch for "big features" section of release notes

On Tue, Aug 3, 2010 at 8:40 PM, Josh Berkus wrote: > Attached is a patch re-arranging some of the features in the first part > of the release notes, as well as adding a few.  The additions are based > on (a) votes on what's a big feature for 9.0, and (b) a desire to match > the features listed els

Re: [DOCS] Documentation improvement for PQgetResult

Daniele Varrazzo writes: > documentation about the PQgetResult function suggests to "[call] > repeatedly until it returns a null pointer, indicating that the > command is done". This has lead psycopg developers to write code with > the pattern: > while (NULL != (res = PQgetResult(conn))) { >

[DOCS] Documentation improvement for PQgetResult

Hello, documentation about the PQgetResult function suggests to "[call] repeatedly until it returns a null pointer, indicating that the command is done". This has lead psycopg developers to write code with the pattern: while (NULL != (res = PQgetResult(conn))) { /* do something with r