[DOCS] A few more fixes to FAQ_DEV

[Devrim GUNDUZ]

Hi,

Attached files fix the link problem in FAQ_DEV.html, remove some parts
related to website development and change the link to the FAQ_DEV.html.

The text version only has the part related to website development.

Please apply.

Regards,
-- 
The PostgreSQL Company - Command Prompt, Inc. 1.503.667.4564
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
Managed Services, Shared and Dedicated Hosting
Co-Authors: plPHP, plPerlNG - http://www.commandprompt.com/

*** FAQ_DEV.old	2006-10-17 11:16:52.0 +0300
--- FAQ_DEV	2006-10-17 11:19:06.0 +0300
***
*** 1,12 
  
Developer's Frequently Asked Questions (FAQ) for PostgreSQL
 
!Last updated: Mon Oct 16 15:24:36 EDT 2006
 
 Current maintainer: Bruce Momjian ([EMAIL PROTECTED])
 
 The most recent version of this document can be viewed at
!http://www.postgresql.org/files/documentation/faqs/FAQ_DEV.html.
   _
 
  General Questions
--- 1,12 
  
Developer's Frequently Asked Questions (FAQ) for PostgreSQL
 
!Last updated: Tue Oct 17 11:15:12 EDT 2006
 
 Current maintainer: Bruce Momjian ([EMAIL PROTECTED])
 
 The most recent version of this document can be viewed at
!http://www.postgresql.org/docs/faqs.FAQ_DEV.html
   _
 
  General Questions
***
*** 560,569 
 [EMAIL PROTECTED] mailing list. The is a project page where the
 source code is available at
 http://gborg.postgresql.org/project/pgweb/projdisplay.php , the code
!for the next version of the website is under the "portal" module. You
!will also find code for the "techdocs" website if you would like to
!contribute to that. A temporary todo list for current website
!development issues is available at http://xzilla.postgresql.org/todo
 
  Technical Questions
  
--- 560,566 
 [EMAIL PROTECTED] mailing list. The is a project page where the
 source code is available at
 http://gborg.postgresql.org/project/pgweb/projdisplay.php , the code
!for the next version of the website is under the "portal" module.
 
  Technical Questions
  
*** FAQ_DEV.html.old	2006-10-17 11:03:19.0 +0300
--- FAQ_DEV.html	2006-10-17 11:17:32.0 +0300
***
*** 13,19 
  Developer's Frequently Asked Questions (FAQ) for
  PostgreSQL
  
! Last updated: Mon Oct  16 15:24:36 EDT 2006
  
  Current maintainer: Bruce Momjian ([EMAIL PROTECTED])
--- 13,19 
  Developer's Frequently Asked Questions (FAQ) for
  PostgreSQL
  
! Last updated: Tue Oct 17 11:15:12 EDT 2006
  
  Current maintainer: Bruce Momjian ([EMAIL PROTECTED])
***
*** 21,27 
  
  The most recent version of this document can be viewed at http://www.postgresql.org/files/documentation/faqs/FAQ_DEV.html";>http://www.postgresql.org/files/documentation/faqs/FAQ_DEV.html.
  
  
   
--- 21,27 
  
  The most recent version of this document can be viewed at http://www.postgresql.org/docs/faqs.FAQ_DEV.html";>http://www.postgresql.org/docs/faqs.FAQ_DEV.html.
  
  
   
***
*** 83,89 
  development?
  
  Download the code and have a look around. See 1.7.
  
  Subscribe to and read the http://archives.postgresql.org/pgsql-hackers";>pgsql-hackers
--- 83,89 
  development?
  
  Download the code and have a look around. See 1.7.
  
  Subscribe to and read the http://archives.postgresql.org/pgsql-hackers";>pgsql-hackers
***
*** 132,138 
  
  You can learn more about these features by consulting the
  archives, the SQL standards and the recommend texts (see 1.10).
  
  1.4) What do I do after choosing an item to
  work on?
--- 132,138 
  
  You can learn more about these features by consulting the
  archives, the SQL standards and the recommend texts (see 1.10).
  
  1.4) What do I do after choosing an item to
  work on?
***
*** 165,171 
  
  Ensure that your patch is generated against the most recent version 
  of the code, which for developers is CVS HEAD. For more on branches in 
! PostgreSQL, see 1.15.
  
  Try to make your patch as readable as possible by following the 
  project's code-layout conventions.  This makes it easier for the
--- 165,171 
  
  Ensure that your patch is generated against the most recent version 
  of the code, which for developers is CVS HEAD. For more on branches in 
! PostgreSQL, see 1.15.
  
  Try to make your patch as readable as possible by following the 
  project's code-layout conventions.  This makes it easier for the
***
*** 196,202 
  
  New feature patches should 

Re: [DOCS] A few more fixes to FAQ_DEV

[Bruce Momjian]

Patch applied.  Thanks.  I only ever need the HTML changes for the FAQ
files that have HTML versions.

---


Devrim GUNDUZ wrote:
-- Start of PGP signed section.
> Hi,
> 
> Attached files fix the link problem in FAQ_DEV.html, remove some parts
> related to website development and change the link to the FAQ_DEV.html.
> 
> The text version only has the part related to website development.
> 
> Please apply.
> 
> Regards,
> -- 
> The PostgreSQL Company - Command Prompt, Inc. 1.503.667.4564
> PostgreSQL Replication, Consulting, Custom Development, 24x7 support
> Managed Services, Shared and Dedicated Hosting
> Co-Authors: plPHP, plPerlNG - http://www.commandprompt.com/
> 

[ Attachment, skipping... ]

[ Attachment, skipping... ]
-- End of PGP section, PGP failed!

-- 
  Bruce Momjian   [EMAIL PROTECTED]
  EnterpriseDBhttp://www.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

Re: [DOCS] [GENERAL] Database users Passwords

[Jeff Davis]

On Tue, 2006-10-17 at 10:41 -0400, DEV wrote:
> Hello all,
> 
>   I have user information in a table that I want to use to add
> users to the user roles tables that are part of postgresql.  My
> question is this: the passwords in my user table are in there as a
> text file with the data being encrypted using the crypt function, is
> there a way I can use this crypt password when I do a “CREATE ROLE
> userid LOGIN PASSWORD 'crypt password' NOSUPERUSER INHERIT NOCREATEDB
> NOCREATEROLE”  I know that in the current CREATE ROLE I have listed
> will take a clear text password and encrypt it for me.  What do I need
> to change to use an encrypted password?
> 

If user is foo and password is bar, do:

=# select md5('barfoo');
LOG:  duration: 0.140 ms  statement: select md5('barfoo');
   md5
--
 96948aad3fcae80c08a35c9b5958cd89
(1 row)

=# create role foo login password 'md596948aad3fcae80c08a35c9b5958cd89'
nosuperuser inherit nocreatedb nocreaterole;

This seems to be lacking in the docs. At least, the only place I found
this information was a user comment in the 8.0 docs. Is this already in
the 8.1 docs? Should we add a description of the way postgresql does the
md5 hashes in the CREATE ROLE section?

Regards,
Jeff Davis


---(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] [GENERAL] Database users Passwords

[Peter Eisentraut]

Jeff Davis wrote:
> This seems to be lacking in the docs. At least, the only place I
> found this information was a user comment in the 8.0 docs. Is this
> already in the 8.1 docs? Should we add a description of the way
> postgresql does the md5 hashes in the CREATE ROLE section?

This has been in the documentation at least as far back as 7.3.

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

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

Re: [DOCS] [GENERAL] Database users Passwords

[Jeff Davis]

On Tue, 2006-10-17 at 21:35 +0200, Peter Eisentraut wrote:
> Jeff Davis wrote:
> > This seems to be lacking in the docs. At least, the only place I
> > found this information was a user comment in the 8.0 docs. Is this
> > already in the 8.1 docs? Should we add a description of the way
> > postgresql does the md5 hashes in the CREATE ROLE section?
> 
> This has been in the documentation at least as far back as 7.3.
> 

I took a second look, and I am not seeing anything in the CREATE ROLE
docs that say you need to concatenate the user to the password before
encrypting with md5. I saw that in a comment in the 8.0 docs, but I
can't find it in the 8.1 docs.

Can you please point me to a specific section?

Regards,
Jeff Davis


---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
   subscribe-nomail command to [EMAIL PROTECTED] so that your
   message can get through to the mailing list cleanly