Re: [DOCS] GIST operators docs [was: [HACKERS] Patch: add GiST support for BOX @> POINT queries]

On Sat, Aug 11, 2012 at 6:04 PM, Tom Lane wrote: > Daniele Varrazzo writes: >> The style of the docs is currently: > >> - in 11.2: on the type page, a list of operators without a single word >> on their meaning, with a link to 9.11 >> <http://www.postgresql.org/d

[DOCS] GIST operators docs [was: [HACKERS] Patch: add GiST support for BOX @> POINT queries]

On Sat, Jul 9, 2011 at 3:29 PM, Hitoshi Harada wrote: > It looks like the time to wrap up. I marked "Return with Feedback" on > this patch, since response from author has not come for a while. Hello, I've just stumbled on the issue mentioned in this thread, which is not fixed in 9.1. To my know

[DOCS] Wrong advisory locks docs in pg_locks

Hello, documentation about advisory locks in the pg_locks view is incorrect/incomplete: the space specifier field is objsubid, not objid, and there is no information about how the key is stored. => select pg_advisory_lock(11

Re: [DOCS] Proposal: syntax highlight in html manual

On Wed, Apr 13, 2011 at 7:34 PM, Peter Eisentraut wrote: > On ons, 2011-04-13 at 11:31 +0100, Daniele Varrazzo wrote: >> If there is, I think the rendering should be performed as a >> post-processing step on the html output and should be a totally >> optional phase: we may

[DOCS] Proposal: syntax highlight in html manual

Hello, when I wrote the docs for the GMP extension (http://pgmp.projects.postgresql.org/) I started improving the syntax highlight produced by pygments (https://bitbucket.org/dvarrazzo/pygments-postgres) for the PostgreSQL SQL dialect. I've also added specific lexers for PL/pgSQL and interactive p

[DOCS] Missing doc for operator args in alter extension

Hello, the documentation for ALTER EXTENSION is missing the description for the arguments of the form ADD OPERATOR name (left_type, right_type). Albeit it's pretty obvious what they are, it is not so obvious what to do for unary operators (i.e. replace the type on the missing side with NONE). Pa

[DOCS] EXTENSION keyword

-- Daniele From e4e932fe3fd6ae54962038c21ca8d0245cd89ecb Mon Sep 17 00:00:00 2001 From: Daniele Varrazzo Date: Mon, 4 Apr 2011 11:03:46 +0100 Subject: [PATCH] Added EXTENSION in the docs keywords list --- doc/src/sgml/keywords.sgml |8 1 files changed, 8 insertions(+), 0 deletions(-) diff --git a/doc/src/sgml/

[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

Re: [DOCS] Please provide stable target anchors

On Wed, Jul 21, 2010 at 8:32 PM, Peter Eisentraut wrote: > On ons, 2010-07-21 at 03:16 +0100, Daniele Varrazzo wrote: >> Attached there is a patch adding an id to the indexterms currently >> referred by psycopg documentation, to be applied to the current head. >> However I&#

Re: [DOCS] Please provide stable target anchors

On Wed, Jul 21, 2010 at 8:32 PM, Peter Eisentraut wrote: > On ons, 2010-07-21 at 03:16 +0100, Daniele Varrazzo wrote: >> I've also played with good results with a script to inject ids in all >> the indexterm, but if the decision is to not provide anchors in the >> midd

Re: [DOCS] Please provide stable target anchors

On Thu, Jul 8, 2010 at 11:01 PM, Peter Eisentraut wrote: > On tor, 2010-07-08 at 20:01 +0100, Daniele Varrazzo wrote: >> I can surely provide you a list, there are just a dozen of them (I'll >> tell you which ones later, now I can't). But then I should bother you >&g

Re: [DOCS] Please provide stable target anchors

On Thu, Jul 8, 2010 at 7:09 PM, Peter Eisentraut wrote: > On tor, 2010-07-08 at 15:54 +0100, Daniele Varrazzo wrote: >> In psycopg documentation I've often referenced specific parts of >> PostgreSQL docs, e.g. libpq functions, using the anchors found in the >> html

[DOCS] Please provide stable target anchors

Hello, In psycopg documentation I've often referenced specific parts of PostgreSQL docs, e.g. libpq functions, using the anchors found in the html docs (see [1] for example). Unfortunately these anchors are not stable and the ones I've linked to have changed, leaving half-broken links referring to