Re: [DOCS] Patch for monitoring.sgml
Added to TODO: > * Allow statistics last vacuum/analyze execution times to be displayed > without requiring stats_row_level to be enabled --- Guillaume Lelarge wrote: > Hi all, > > This patch adds a sentence on monitoring.sgml explaining that > stats_row_level needs to be enabled if user wants to get last > vacuum/analyze execution time. > > This patch can be applied on 8.2 branch and HEAD. > > Regards. > > > -- > Guillaume. > http://www.postgresqlfr.org > http://docs.postgresqlfr.org [ text/x-diff is unsupported, treating like TEXT/PLAIN ] > Index: doc/src/sgml/monitoring.sgml > === > RCS file: /projects/cvsroot/pgsql/doc/src/sgml/monitoring.sgml,v > retrieving revision 1.40.2.2 > diff -r1.40.2.2 monitoring.sgml > 157a158,159 > > also controls vacuum and analyze > >last execution times (manual and daemon). > > ---(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 -- Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us EnterpriseDB http://postgres.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + -- Sent via pgsql-docs mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs
[DOCS] order of entries in admin docs
I was just looking for something in the admin docs, and it seems like the ordering of sections is sub-optimal. 17. Operating System Environment 18. Server Configuration 19. Database Roles and Privileges 20. Managing Databases 21. Client Authentication Seems that Client Authentication should come right after Server Configuration. After all, how is someone going to handle roles and database creation before they've authenticated? Is there some reason for the order that I'm missing? Is it an easy change? I'd be happy to try and make a patch for something like that if there's a chance of it getting through / my figuring out how to do it in the docs. -- Sent via pgsql-docs mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs
Re: [DOCS] order of entries in admin docs
Scott Marlowe escribió: > Seems that Client Authentication should come right after Server > Configuration. After all, how is someone going to handle roles and > database creation before they've authenticated? Is there some reason > for the order that I'm missing? Is it an easy change? I'd be happy > to try and make a patch for something like that if there's a chance of > it getting through / my figuring out how to do it in the docs. Yeah, see postgres.sgml -- changing the order is just a matter of moving where the entries appear. The current order is probably just historical. -- Alvaro Herrerahttp://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support -- Sent via pgsql-docs mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs
Re: [DOCS] order of entries in admin docs
"Scott Marlowe" <[EMAIL PROTECTED]> writes: > I was just looking for something in the admin docs, and it seems like > the ordering of sections is sub-optimal. > 17. Operating System Environment > 18. Server Configuration > 19. Database Roles and Privileges > 20. Managing Databases > 21. Client Authentication > Seems that Client Authentication should come right after Server > Configuration. After all, how is someone going to handle roles and > database creation before they've authenticated? Well, until you know what a role is, the client auth discussion might not make too much sense to you... I'm not wedded to the current ordering but I'm not sure it's silly either. Something else that ought to be considered here is that now that we have CONNECT privilege for databases, manipulating privileges is a lot saner way to control who-can-connect-where than setting up fancy combinations of user and database entries in pg_hba.conf. AFAIR there is no mention of this alternative in Chapter 21, but it seems like there ought to be. With your proposed reorganization, that would become a forward reference; is that OK? 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] order of entries in admin docs
On Tue, Mar 11, 2008 at 10:36 AM, Tom Lane <[EMAIL PROTECTED]> wrote: > "Scott Marlowe" <[EMAIL PROTECTED]> writes: > > I was just looking for something in the admin docs, and it seems like > > the ordering of sections is sub-optimal. > > > 17. Operating System Environment > > 18. Server Configuration > > 19. Database Roles and Privileges > > 20. Managing Databases > > 21. Client Authentication > > > Seems that Client Authentication should come right after Server > > Configuration. After all, how is someone going to handle roles and > > database creation before they've authenticated? > > Well, until you know what a role is, the client auth discussion might > not make too much sense to you... > > I'm not wedded to the current ordering but I'm not sure it's silly > either. > > Something else that ought to be considered here is that now that we have > CONNECT privilege for databases, manipulating privileges is a lot saner > way to control who-can-connect-where than setting up fancy combinations > of user and database entries in pg_hba.conf. AFAIR there is no mention > of this alternative in Chapter 21, but it seems like there ought to be. > With your proposed reorganization, that would become a forward > reference; is that OK? I've deleted and rewritten this email like 4 times... The more I read the docs, the more moving client authentication seems to make sense. In fact, the authentication problems section is probably the perfect final bit to the Connections and Authentication section. I'd move it up a level, so that it looked something like this: 18.3. Connections and Authentication 18.3.1. Connection Settings 18.3.2. Security and Authentication 18.3.3. The pg_hba.conf file 18.3.4. Authentication methods 18.3.5. Authentication problems Unless a different level of indentation makes more sense, which I could totally understand. It definitely follows the flow of setting up a pg server better for me. I might even move the pg_hba.conf file to 18.3.1 up there. It is pretty much a firewall. -- Sent via pgsql-docs mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs
