Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id 5109E1337B80 for ; Sat, 30 Apr 2011 00:45:16 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 33074-09 for ; Sat, 30 Apr 2011 03:45:04 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.10]) by mail.postgresql.org (Postfix) with ESMTP id 42E001337999 for ; Sat, 30 Apr 2011 00:45:04 -0300 (ADT) Received: from [192.168.1.6] (mail.highperformancepostgresql.com [71.179.240.8]) by mrelayeu.kundenserver.de (node=mrbap1) with ESMTP (Nemesis) id 0MWhPH-1QHWQ00tyN-00XXiN; Sat, 30 Apr 2011 05:45:03 +0200 Message-ID: <4DBB8614.70307@2ndQuadrant.com> Date: Fri, 29 Apr 2011 23:46:28 -0400 From: Greg Smith User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20110307 Icedove/3.0.11 MIME-Version: 1.0 To: pgsql-docs Subject: Documentation tweaks: ALTER USER, statement-based middleware Content-Type: multipart/mixed; boundary="------------060708070508030900050704" X-Provags-ID: V02:K0:wrVuoebqHrKs71TOS0IgYMctG41TXtK/tGnyTuDeX0j SU7L/NgnnMpZnayhgG1/KaQFUCFwlcrYSkjoqf4fUYRMDOSpdz HIlIjZoD2m1vCZkqvorZMJmFSEOCcvJfnAWdGPWTxYjEu67NtJ 1Or7rQkraREm6nx7renOG4QRHaVCpevHLQSxXw8nlz6UA9EB3/ HZ9ve3cHVM554y6IBhbsbk0quOo4tKCHUfoGt4pkfI= X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.1 tagged_above=-5 required=5 tests=BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SARE_BAYES_5x8=0.8 X-Spam-Level: X-Archive-Number: 201104/104 X-Sequence-Number: 6675 This is a multi-part message in MIME format. --------------060708070508030900050704 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Two small patches attached, based on recent documentation comments suggested on the web site. First alters a few places that ALTER USER is suggested, mainly in the context of changing per-user settings. If you're reading the HTML documentation, and you click on ALTER USER, it takes you to a slim page that tells you what you really wanted was ALTER ROLE. That's kind of wasteful, and thus the idea to go directly there. Original doc suggestion from Grzegorz Szpetkowski, I found a few more places to tweak when assembling the patch. Wording may be a bit weird in spots though, so I'm not sure this is necessarily an improvement in all cases. Right now the description around these says things like "debugging could be enabled for all sessions under a given user name by setting this parameter with ALTER USER SET". Making that ALTER ROLE instead saves that page redirect shuffle for document readers, but is it as clear to people who may not know user==role? Hard to say. Second doc patch is more straightforward, and based on an observation by James Bruce. The description of how read/write traffic can be scaled with statement-based middleware was so terse that it was hard to understand. His suggested rewording shows he didn't follow the idea it was trying to communicate at all. The updated wording I'm providing is more explicit and shouldn't be as confusing. While in there, I also fixed the obsolete mention of Sequoia with the current Continuent project name of Tungsten; http://joomla.aws.continuent.com/community/lab-projects/sequoia documents the name change. -- Greg Smith 2ndQuadrant US greg@2ndQuadrant.com Baltimore, MD PostgreSQL Training, Services, and 24x7 Support www.2ndQuadrant.us --------------060708070508030900050704 Content-Type: text/x-patch; name="less-alter-user.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="less-alter-user.patch" diff --git a/doc/src/sgml/client-auth.sgml b/doc/src/sgml/client-auth.sgml index 44e1f47..633feff 100644 --- a/doc/src/sgml/client-auth.sgml +++ b/doc/src/sgml/client-auth.sgml @@ -786,7 +786,7 @@ omicron bryanh guest1 each database user is stored in the pg_authid system catalog. Passwords can be managed with the SQL commands and - , + , e.g., CREATE USER foo WITH PASSWORD 'secret'. If no password has been set up for a user, the stored password is null and password authentication will always fail for that user. diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml index 1b8e5a5..7c91a09 100644 --- a/doc/src/sgml/config.sgml +++ b/doc/src/sgml/config.sgml @@ -135,7 +135,7 @@ env PGOPTIONS='-c geqo=off' psql Furthermore, it is possible to assign a set of parameter settings to a user or a database. Whenever a session is started, the default settings for the user and database involved are loaded. The - commands + commands and , respectively, are used to configure these settings. Per-database settings override anything received from the @@ -702,7 +702,7 @@ SET ENABLE_SEQSCAN TO OFF; When a password is specified in or - + without writing either ENCRYPTED or UNENCRYPTED, this parameter determines whether the password is to be encrypted. The default is on @@ -4959,7 +4959,7 @@ dynamic_library_path = 'C:\tools\postgresql;H:\my_project\lib;$libdir' libraries to be loaded into specific sessions without an explicit LOAD command being given. For example, debugging could be enabled for all sessions under a given user name by setting - this parameter with ALTER USER SET. + this parameter with ALTER ROLE SET. diff --git a/doc/src/sgml/libpq.sgml b/doc/src/sgml/libpq.sgml index f53702c..6e9e42c 100644 --- a/doc/src/sgml/libpq.sgml +++ b/doc/src/sgml/libpq.sgml @@ -6168,7 +6168,7 @@ myEventProc(PGEventId evtId, void *evtInfo, void *passThrough) The following environment variables can be used to specify default behavior for each PostgreSQL session. (See - also the + also the and commands for ways to set default behavior on a per-user or per-database basis.) --------------060708070508030900050704 Content-Type: text/x-patch; name="middleware-reads.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="middleware-reads.patch" diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml index 74684f7..cfb8a2b 100644 --- a/doc/src/sgml/high-availability.sgml +++ b/doc/src/sgml/high-availability.sgml @@ -188,9 +188,10 @@ protocol to make nodes agree on a serializable transactional order. With statement-based replication middleware, a program intercepts every SQL query and sends it to one or all servers. Each server - operates independently. Read-write queries are sent to all servers, - while read-only queries can be sent to just one server, allowing - the read workload to be distributed. + operates independently. Read-write queries must be sent to all servers, + so that every server receives any changes. But read-only queries can be + sent to just one server, allowing the read workload to be distributed + among them. @@ -209,8 +210,8 @@ protocol to make nodes agree on a serializable transactional order. transactions either commit or abort on all servers, perhaps using two-phase commit ( and . - Pgpool-II and Sequoia are examples of - this type of replication. + Pgpool-II and Continuent Tungsten + are examples of this type of replication. --------------060708070508030900050704--