Re: [DOCS] Tips needed for contrib doc

2007-10-12 Thread Albert Cervera i Areny
The problem with this approach is dblink[1], for example, in which I can't use 
reference (as I've already used for dblink itself). I will probably have to 
use  in theses cases then...

[1] http://www.nan-tic.com/ftp/pgdoc/dblink.html

A Dijous 11 Octubre 2007, Tom Lane va escriure:
> Guillaume Lelarge <[EMAIL PROTECTED]> writes:
> > The only (or simplest) way to have one page per module is to use the
> > reference part.
>
> If the plan is one module per page, why not handle 'em just like the
> current command and client reference pages?  Add another list to
> reference.sgml, and away you go.
>
>   regards, tom lane



-- 
Albert Cervera i Areny
http://www.NaN-tic.com

---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
   choose an index scan if your joining column's datatypes do not
   match


Re: [DOCS] Tips needed for contrib doc

2007-10-12 Thread Peter Eisentraut
Am Mittwoch, 10. Oktober 2007 schrieb Albert Cervera i Areny:
> - I can't make this "contrib" doc a part because Reference already
> is a part and can't be nested.

The Reference things in DocBook are mostly to support legacy man pages, and 
man pages are not necessary the greatest format to document everything.  What 
is your reason that you want this as a reference rather than a part with 
chapters?

-- 
Peter Eisentraut
http://developer.postgresql.org/~petere/

---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings


[DOCS] FAQ corrections

2007-10-12 Thread Ian Barwick
Hi

attached some minor corrections, mainly completion of removal of 
the  "relation with OID # does not exist" item, and some URL corrections.

Ian Barwick
Index: FAQ.html
===
RCS file: /projects/cvsroot/pgsql/doc/src/FAQ/FAQ.html,v
retrieving revision 1.394
diff -c -r1.394 FAQ.html
*** FAQ.html	9 Oct 2007 20:13:11 -	1.394
--- FAQ.html	12 Oct 2007 18:03:12 -
***
*** 141,148 
  developers spread throughout the world and communicating via the
  Internet. It is a community project and is not controlled by any
  company. To get involved, see the developer's FAQ at http://www.postgresql.org/files/documentation/faqs/FAQ_DEV.html";>
! http://www.postgresql.org/files/documentation/faqs/FAQ_DEV.html
  
  
  1.2) Who controls PostgreSQL?
--- 141,148 
  developers spread throughout the world and communicating via the
  Internet. It is a community project and is not controlled by any
  company. To get involved, see the developer's FAQ at http://www.postgresql.org/docs/faqs.FAQ_DEV.html";>
! http://www.postgresql.org/docs/faqs.FAQ_DEV.html
  
  
  1.2) Who controls PostgreSQL?
***
*** 334,343 
  There are a number of PostgreSQL books available for purchase.  One
  of the most popular ones is by Korry Douglas.  A list of book reviews
  can be found at http://techdocs.postgresql.org/techdocs/bookreviews.php";>http://techdocs.postgresql.org/techdocs/bookreviews.php.
  There is also a collection of PostgreSQL technical articles at http://techdocs.postgresql.org/";>http://techdocs.postgresql.org/.
  
  The command line client program psql has some \d commands to show
  information about types, operators, functions, aggregates, etc. - use \? to 
--- 334,343 
  There are a number of PostgreSQL books available for purchase.  One
  of the most popular ones is by Korry Douglas.  A list of book reviews
  can be found at http://www.postgresql.org/docs/books/";>http://www.postgresql.org/docs/books/.
  There is also a collection of PostgreSQL technical articles at http://www.postgresql.org/docs/techdocs";>http://www.postgresql.org/docs/techdocs.
  
  The command line client program psql has some \d commands to show
  information about types, operators, functions, aggregates, etc. - use \? to 
***
*** 349,358 
  SQL?
  
  First, consider the PostgreSQL-specific books mentioned above.
! Another one is "Teach Yourself SQL in 21 Days, Second Edition"
! at http://members.tripod.com/er4ebus/sql/index.htm";>http://members.tripod.com/er4ebus/sql/index.htm.
! Many of our users like The Practical SQL Handbook,
  Bowman, Judith S., et al., Addison-Wesley. Others like The
  Complete Reference SQL, Groff et al., McGraw-Hill.
  
--- 349,355 
  SQL?
  
  First, consider the PostgreSQL-specific books mentioned above.
! Many of our users also like The Practical SQL Handbook,
  Bowman, Judith S., et al., Addison-Wesley. Others like The
  Complete Reference SQL, Groff et al., McGraw-Hill.
  
***
*** 541,547 
  
  A number of postgresql.conf settings affect performance.
  For more details, see http://www.postgresql.org/docs/current/static/runtime.html";>
  Administration Guide/Server Run-time Environment/Run-time
  Configuration for a full listing, and for commentary see http://www.varlena.com/varlena/GeneralBits/Tidbits/annotated_conf_e.html";>
--- 538,544 
  
  A number of postgresql.conf settings affect performance.
  For more details, see http://www.postgresql.org/docs/current/static/runtime-config.html";>
  Administration Guide/Server Run-time Environment/Run-time
  Configuration for a full listing, and for commentary see http://www.varlena.com/varlena/GeneralBits/Tidbits/annotated_conf_e.html";>
***
*** 1042,1060 
  
  It is easy using set-returning functions, 
  http://www.postgresql.org/docs/techdocs.17";>
! http://www.postgresql.org/docs/techdocs.17.
! 
! 4.19) Why do I get "relation with OID #
! does not exist" errors when accessing temporary tables in PL/PgSQL
! functions?
! 
! PL/PgSQL caches function scripts, and an unfortunate side effect
! is that if a PL/PgSQL function accesses a temporary table, and that
! table is later dropped and recreated, and the function called again,
! the function will fail because the cached function contents still
! point to the old temporary table. The solution is to use
! EXECUTE for temporary table access in PL/PgSQL. This
! will cause the query to be reparsed every time.
  
  4.19) What replication solutions are available?
  
--- 1039,1045 
  
  It is easy using set-returning functions, 
  http://www.postgresql.org/docs/techdocs.17";>
! http://www.postgresql.org/docs/techdocs.17.
  
 

Re: [DOCS] Tips needed for contrib doc

2007-10-12 Thread Albert Cervera i Areny
Not that I want to make each module a reference. With previous discussions we 
seemed to agree that:

- It should go into the References part of the documentation (right 
after "III. PostgreSQL Server Applications).
- Each module docs should be in a single page, mainly because some contrib 
modules have/require very little documentation.

So it seems that the only way of achieving both things is to make each contrib 
module a  inside a new . I don't like this 
idea, among other things because dblink won't be abe to be treated as a 
 which I think is appropiate in this case.

If you've got another solution for this, it'll be very welcome!

A Divendres 12 Octubre 2007, Peter Eisentraut va escriure:
> Am Mittwoch, 10. Oktober 2007 schrieb Albert Cervera i Areny:
> > - I can't make this "contrib" doc a part because Reference
> > already is a part and can't be nested.
>
> The Reference things in DocBook are mostly to support legacy man pages, and
> man pages are not necessary the greatest format to document everything. 
> What is your reason that you want this as a reference rather than a part
> with chapters?



-- 
Albert Cervera i Areny
http://www.NaN-tic.com

---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster


Re: [DOCS] FAQ corrections

2007-10-12 Thread Bruce Momjian

Patch applied.  Thanks.

---


Ian Barwick wrote:
> Hi
> 
> attached some minor corrections, mainly completion of removal of 
> the  "relation with OID # does not exist" item, and some URL corrections.
> 
> Ian Barwick

[ Attachment, skipping... ]

> 
> ---(end of broadcast)---
> TIP 3: Have you checked our extensive FAQ?
> 
>http://www.postgresql.org/docs/faq

-- 
  Bruce Momjian  <[EMAIL PROTECTED]>http://momjian.us
  EnterpriseDB http://postgres.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings