[DOCS] Mention libpq env. and pgpass in psql manual page

2005-02-10 Thread Bruce Momjian
I have committed to CVS HEAD and 8.0.X:

---

Mention that some psql environment variables come from libpq and note
more variables can be found in the libpq manual section.

Mention .pgpass in the psql manual page section dealing with connection
parameters and point to the libpq section for more details.

Backpatch to 8.0.X.

-- 
  Bruce Momjian|  http://candle.pha.pa.us
  [email protected]   |  (610) 359-1001
  +  If your life is a hard drive, |  13 Roberts Road
  +  Christ can be your backup.|  Newtown Square, Pennsylvania 19073
Index: doc/src/sgml/ref/psql-ref.sgml
===
RCS file: /cvsroot/pgsql/doc/src/sgml/ref/psql-ref.sgml,v
retrieving revision 1.132
diff -c -c -r1.132 psql-ref.sgml
*** doc/src/sgml/ref/psql-ref.sgml  22 Jan 2005 23:22:19 -  1.132
--- doc/src/sgml/ref/psql-ref.sgml  11 Feb 2005 04:14:48 -
***
*** 348,354 
-u


!   Makes psql prompt for the user name and
password before connecting to the database.

  
--- 348,354 
-u


!   Forces psql to prompt for the user name and
password before connecting to the database.

  
***
*** 406,426 
--password


!   Cause psql to prompt for a
!   password before connecting to a database. This will remain set for
!   the entire session, even if you change the database connection
!   with the meta-command \connect.

  

!   In the current version, psql
!   automatically issues a password prompt whenever the server
!   requests password authentication. Because this is currently based
!   on a hack, the automatic recognition might mysteriously fail,
!   hence this option to force a prompt. If no password prompt is
!   issued and the server requires password authentication, the
!   connection attempt will fail.


  
  
--- 406,430 
--password


!   Forces psql to prompt for a
!   password before connecting to a database.  

  

!   psql should automatically prompt for a
!   password whenever the server requests password authentication.
!   However, currently password request detection is not totally
!   reliable, hence this option to force a prompt. If no password
!   prompt is issued and the server requires password authentication,
!   the connection attempt will fail.

+ 
+   
+   This option will remain set for the entire session, even if you
+   change the database connection with the meta-command
+   \connect.
+   
+ 

  
  
***
*** 508,514 
  some typing by setting the environment variables
  PGDATABASE, PGHOST,
  PGPORT and/or PGUSER to appropriate
! values.
  
  
  
--- 512,521 
  some typing by setting the environment variables
  PGDATABASE, PGHOST,
  PGPORT and/or PGUSER to appropriate
! values. (For additional environment variables, see .) It is also convenient to have a
! ~/.pgpass file to avoid regularly having to type in
! passwords. See  for more information.
  
  
  
***
*** 2460,2466 
  
  
   
!   Default database to connect to
   
  
 
--- 2467,2473 
  
  
   
!   Default connection database
   
  
 

---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?

   http://www.postgresql.org/docs/faq


Re: [DOCS] Default Values Section

2005-02-10 Thread Bruce Momjian

OK, I updated the documentation to add a comment on that line:

SELECT CURRENT_TIMESTAMP;
SELECT now();
SELECT TIMESTAMP 'now';  -- incorrect for use with DEFAULT


---

Lourival Oliveira wrote:
> I have a problem reading the "5.3 Default Values" Section of 
> Postgresql8.0.0-rc1 documentation. In this section there are nothing about 
> using 'now' constant. I think which there are a conflict with a note about 
> 'now' in section "9.9. Date/Time Functions and Operators" which show the way 
> to achieve the desired behavior. See:
> 
> 5.3. Default Values
> 
> ...
> 
> The default value may be a scalar expression, which will be evaluated 
> whenever the default value is inserted (not when the table is created).
> 
> 
> 9.9. Date/Time Functions and Operators
> 
> ...
> 
> SELECT CURRENT_TIMESTAMP;
> SELECT now();
> SELECT TIMESTAMP 'now';
> Note: You do not want to use the third form when specifying a DEFAULT clause 
> while creating a table. The system will convert now to a timestamp as soon 
> as the constant is parsed, so that when the default value is needed, the 
> time of the table creation would be used! The first two forms will not be 
> evaluated until the default value is used, because they are function calls. 
> Thus they will give the desired behavior of defaulting to the time of row 
> insertion.
> 
> I think which a simple reference to any unpredictable behavior must be 
> placed here to avoid confusion when anybody don't reach the desired behavior 
> when use default values.
> 
> What think you about my suggestion?
> 
> Wait replies, Tanks.
> 
> Lourival Oliveira da Silva
> 
> PS: Sorry by my poor English. 
> 
> 
> 
> ---(end of broadcast)---
> TIP 3: 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
> 

-- 
  Bruce Momjian|  http://candle.pha.pa.us
  [email protected]   |  (610) 359-1001
  +  If your life is a hard drive, |  13 Roberts Road
  +  Christ can be your backup.|  Newtown Square, Pennsylvania 19073

---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?

   http://www.postgresql.org/docs/faq


Re: [DOCS] FAQ on oids is out of date.

2005-02-10 Thread Bruce Momjian

Yep, the FAQ was _very_ out of date.  If you look at it now you will
find a lot of it has been updated.

Thanks.

---

Kris Jurka wrote:
> 
> http://www.postgresql.org/files/documentation/faqs/FAQ.html#4.16
> 
> The FAQ on oids is out of date.  It claims that they are globally unique 
> and that no one has ever rolled over the oid counter.  This should be 
> changed to actively discourage their use.
> 
> Kris Jurka
> 
> ---(end of broadcast)---
> TIP 9: the planner will ignore your desire to choose an index scan if your
>   joining column's datatypes do not match
> 

-- 
  Bruce Momjian|  http://candle.pha.pa.us
  [email protected]   |  (610) 359-1001
  +  If your life is a hard drive, |  13 Roberts Road
  +  Christ can be your backup.|  Newtown Square, Pennsylvania 19073

---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?

   http://www.postgresql.org/docs/faq


Re: [DOCS] Updated Russian translation of the FAQ

2005-02-10 Thread Bruce Momjian

Thanks, applied to CVS HEAD and 8.0.X.

---

Viktor Vislobokov wrote:
> There is updated Russian translation of the FAQ in attachment.
> 
> -- 
> With best wishes,
> Victor Vislobokov
> Perm. Russia
> 
> 
> 

[ application/x-gzip is not supported, skipping... ]

-- 
  Bruce Momjian|  http://candle.pha.pa.us
  [email protected]   |  (610) 359-1001
  +  If your life is a hard drive, |  13 Roberts Road
  +  Christ can be your backup.|  Newtown Square, Pennsylvania 19073

---(end of broadcast)---
TIP 3: 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