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

2010-08-04 Thread Josh Berkus 
All,

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 elsewhere, such as the press kit.

-- 
-- Josh Berkus
-
Josh Berkus   PostgreSQL Experts Inc.
CEO   database professionals
[email protected] www.pgexperts.com
1-888-743-9778 x.508  San Francisco
Index: release-9.0.sgml
===
RCS file: /projects/cvsroot/pgsql/doc/src/sgml/release-9.0.sgml,v
retrieving revision 2.44
diff -c -r2.44 release-9.0.sgml
*** release-9.0.sgml	29 Jul 2010 21:18:11 -	2.44
--- release-9.0.sgml	4 Aug 2010 00:25:34 -
***
*** 12,27 
  

 Overview
- 
 
  Based on overwhelming user demand, this release of
  PostgreSQL adds features that have been requested
  for years, like easy-to-use replication, a mass permission
  facility, and anonymous blocks. While past major releases have
! been conservative in their scope, this release shows a
! bold new desire to provide facilities that new and existing
! users of PostgreSQL will embrace. This has all
! been done with few incompatibilities. Major enhancements are:
 
  
 
--- 12,27 
  

 Overview
 
  Based on overwhelming user demand, this release of
  PostgreSQL adds features that have been requested
  for years, like easy-to-use replication, a mass permission
  facility, and anonymous blocks. While past major releases have
! been quite conservative in their scope, this release shows a
! bold new desire to provide facilities that every new and existing
! user of PostgreSQL will embrace. This has all
! been done with few incompatibilities. The major areas of
! enhancement are:
 
  
 
***
*** 29,41 
  
  
  
- 
   
!   Built-in, binary, log-based replication.  This advance consists of two
!   features: Hot Standby allows continuous archive standby database servers
!   to accept read-only queries, and Streaming Replication allows continuous
!   archive (WAL) files to be streamed over a network port to a
!   standby database server.
   
  
  
--- 29,39 
  
  
  
   
!   Built-in, binary, log-based replication.  This advance consists of two features:
!   Hot Standby allows continuous archive standby database servers to accept read-only
!   queries, and Streaming Replication allows continuous archive (WAL) files 
!   to be streamed over a network port to a standby database server.
   
  
  
***
*** 53,64 
  
  
   
Broadly enhanced stored procedure support.
The DO statement permits
!   anonymous code blocks.  Functions can now be called using named
!   parameters.  PL/pgSQL is now installed by default, and PL/Perl and
!   PL/Python have been enhanced in several ways, including support for
!   Python3.
   
  
  
--- 51,78 
  
  
   
+   Add support for compiling on 64-bit
+   Windows and running in 64-bit
+   mode.
+  
+ 
+ 
+ 
+  
Broadly enhanced stored procedure support.
The DO statement permits
!   ad-hoc or anonymous code blocks.  Functions can now be called using named
!   parameters.  PL/pgSQL is now installed by default, and PL/Perl and PL/Python
!   have been enhanced in several ways, including support for Python3.
!  
! 
! 
! 
!  
!   More advanced reporting queries with additional windowing functions 
!   (PRECEDING and FOLLOWING) and the ability to ORDER BY inside aggregate
!   functions.
   
  
  
***
*** 66,72 
   
Triggers now support two new features,
SQL-compliant per-column triggers, and
conditional trigger execution.
   
  
--- 80,86 
   
Triggers now support two new features,
SQL-compliant per-column triggers, and 
conditional trigger execution.
   
  
***
*** 80,95 
  
  
   
!   Exclusion constraints let database designers define uniqueness
!   based on complex criteria, including for non-scalar data such
!   as time periods, ranges and arrays.
   
  
  
  
   
The LISTEN/NOTIFY
feature has been overhauled to make it into
a high-performance event queuing system.  It now stores
events in a memory-based queue, and it now allows delivery
--- 94,109 
  
  
   
!   New and enhanced security features, including RADIUS authentication,
!   LDAP authentication improvements, and the new checkpassword optional module
!   for te

[DOCS] PQescapeLiteral(), PQescapeIdentifier() documented with invalid signatures.

2010-08-04 Thread Dmitriy Igrishin 
Hey all,

Actual signatures of libpq's functions PQescapeLiteral(),
PQescapeIdentifier()
is
char *PQescapeLiteral(PGconn *conn, const char *str, size_t len)
char *PQescapeIdentifier(PGconn *conn, const char *str, size_t len)

that differs from signatures provided in the documentation here

http://www.postgresql.org/docs/9.0/static/libpq-exec.html#LIBPQ-EXEC-ESCAPE-STRING

Regards,
Dmitriy

Re: [DOCS] PQescapeLiteral(), PQescapeIdentifier() documented with invalid signatures.

2010-08-04 Thread Tom Lane 
Dmitriy Igrishin  writes:
> Actual signatures of libpq's functions PQescapeLiteral(),
> PQescapeIdentifier()
> is
> char *PQescapeLiteral(PGconn *conn, const char *str, size_t len)
> char *PQescapeIdentifier(PGconn *conn, const char *str, size_t len)

> that differs from signatures provided in the documentation here
> http://www.postgresql.org/docs/9.0/static/libpq-exec.html#LIBPQ-EXEC-ESCAPE-STRING

Wow ... I can understand missing the "const" declarations, but getting
the return type wrong is pretty bad :-(.  Amazing nobody caught this
before.  Thanks, will fix!

regards, tom lane

-- 
Sent via pgsql-docs mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs

Re: [DOCS] Please provide stable target anchors

2010-08-04 Thread Daniele Varrazzo 
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've tried to render the html docs with the head itself and I
>> see anchors are not generated anymore, while they are generated by the
>> makefile shipped in 8.4.4. Is this a decision or it just happened? In
>> the former case there is no point in applying the patch then.
>
> Hmm, never noticed that, but it appears to come from the changes we made
> in the build process to not build the index twice and thus speed up the
> build.
>
>> 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
>> middle of the page I think you wouldn't be interested in it.
>
> I think it's a bit weird to link to indexentry elements.  I can't quite
> wrap my head around it.  I think you could just as well link to the
> varlistentry elements or some other element close by.  Check out how we
> link to the configuration parameters in config.sgml.
>
> Btw., try to use some kind of hierarchical scheme for the id's.  If
> something is in the libpq chapter, use something like
> id="libpq-pqtransactionstatus".

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 .

lobj.sgml doesn't use libpq so I've added ids to the sect2 tags, which
are local enough. I've added them manually as are not so many.

Patches are available from the git clone at
. I've prepared patches for 8.4
and 9.0 (branches "fixanchor-8-4" and "fixanchor-9-0").

Feedback is appreciated. Regards.

-- Daniele

-- 
Sent via pgsql-docs mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs