Re: [DOCS] Online documentation unclear about authentication defaults

[bubblboy]

Alvaro Herrera wrote:

bubblboy wrote:

Hi,

After following the postgresql tutorial for setting up a postgresql 
server [1] I noticed that I could log in without entering my password. 
The documentation did not tell me this (maybe I overlooked it), 
eventhough it does show you how to create roles with passwords. In my 
opinion it would be a good idea to include a warning like "the default 
installation trusts everybody that can make a connection to the 
database" because it could lead to some (problematic) confusions.


I didn't check extensively in the docs to see if there actually was such 
a warning, particularly because I felt that if there was, it was 
probably not prominent enough (or I would have noticed). Sorry if there 
was indeed a big warning splattered over the tutorial somewhere.


The tutorial indeed neglects warning you about that, but initdb doesn't.
It outputs these lines

WARNING: enabling "trust" authentication for local connections
You can change this by editing pg_hba.conf or using the -A option the
next time you run initdb.


Maybe this is not strong enough, or not scary enough?


Hmm,

You are right, I ran initdb a few weeks ago and continued today. 
Personally, I would say that it wouldn't be a bad idea to include a 
second warning in the documentation nonetheless, just to emphasize it 
(or maybe make the initdb message a little more prominent - who knows). 
I can imagine that I saw all that output and thought "oh well, I'm 
following the tutorial so this won't be very interesting", but maybe 
(probably) that's just plain stupid :)


Greetings,
bb

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

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

Re: [DOCS] [HACKERS] [PATCHES] [PERFORM] Direct I/O issues

[Bruce Momjian]

Greg Smith wrote:
> On Fri, 24 Nov 2006, Bruce Momjian wrote:
> 
> > OK, I modified test_fsync.c by copying the defines from xlog.c, and
> > fixed the O_DIRECT alignment and check write()/fsync().
> 
> I just tested your new test_fsync as included in the 8.2rc1, and it's 
> working perfectly for me now on Linux.  All the O_SYNC writes using 
> O_DIRECT are reporting realistic timings.  I'm happy that this code is 
> working as it should and appreciate the quick response.  I still think the 
> wal_sync_method documentation deserves an update noting that O_DIRECT is 
> used when available with the sync write methods.

O_DIRECT mention added, and backpatched to 8.2.X.

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

  + If your life is a hard drive, Christ can be your backup. +
Index: doc/src/sgml/config.sgml
===
RCS file: /cvsroot/pgsql/doc/src/sgml/config.sgml,v
retrieving revision 1.108
diff -c -c -r1.108 config.sgml
*** doc/src/sgml/config.sgml	1 Feb 2007 00:28:16 -	1.108
--- doc/src/sgml/config.sgml	8 Feb 2007 03:52:01 -
***
*** 1385,1390 
--- 1385,1391 
  Not all of these choices are available on all platforms.
  The default is the first method in the above list that is supported
  by the platform.
+ The open_* options also use O_DIRECT if available.
  This parameter can only be set in the postgresql.conf
  file or on the server command line.
 

---(end of broadcast)---
TIP 4: Have you searched our list archives?

   http://archives.postgresql.org