Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1axxyx-0002ev-ME for pgsql-docs@arkaria.postgresql.org; Wed, 04 May 2016 14:40:55 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1axxyx-0004fk-5L for pgsql-docs@arkaria.postgresql.org; Wed, 04 May 2016 14:40:55 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1axxyv-0004e4-6s for pgsql-docs@postgresql.org; Wed, 04 May 2016 14:40:53 +0000 Received: from mail-lf0-x233.google.com ([2a00:1450:4010:c07::233]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1axxys-0000nC-E1 for pgsql-docs@postgresql.org; Wed, 04 May 2016 14:40:51 +0000 Received: by mail-lf0-x233.google.com with SMTP id y84so62879066lfc.0 for ; Wed, 04 May 2016 07:40:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to; bh=/alb+vq/oX312q10CaFa28IsxOYEz841NczMzJkLK/4=; b=yW3oA+BgrYAoDlR28OoOIMfeQl5P8LFckpT286B1dmhDBaGKHJ/7yhFlaY8qwkWLG+ uUMroWqhqIEMeHZVriXXJlRDGIOVwXIqDOBiDe7ZHsoe55Ee/2ojjgybbOVRrzjBLfip fC/XQhosZdqpbmz8/pg5EiI+1Ay69RHV2vD+fNjLnvqNTYY4U8QNYL1+Go1fO3EDKvtF 0vLX5HMv5H4vX+NqJKjIO517Yyp8WV14d5VmfeSKROHyQXbAqYI9iAFLyKObytQaHBSH 7ORSL/O7gUVxFJ+tQSQKTsxov1gJv9WJPTToxEybBF0YjxZJaC6H+45h2/8HHjZHWVdX 5g7g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to; bh=/alb+vq/oX312q10CaFa28IsxOYEz841NczMzJkLK/4=; b=GyJI2ablu/J+4WSQJnTTTtycbK05mLffd+F8RkJVlSHIYtE+umbOafFBo3F8UOzMLf 6l9OOdrl59cYIsrd1iLLnnNPquChycV7yawdQ/m4o28O8bxNuK531ZUzCp8Y+T96tbHS MKEAJ2ieqVGWEay7EoyC0ZynP9/3U5oSOvhQrkduiC+qJR8fyu7DDuX1DbrNbmrd/rhC y+SKvj+45ldJ/M7ptiJ8PqrTnwSEJuNrP4xbnjbiTs8/DD8Ok80x2PtXi9K5IQM+Ag9K gZrJFVjAz3YUBTRR7THAeDSkRREl55CFZnuSTU0l/rxVWyuaqnUzHnPqzYgkcRJxTBh8 HL+g== X-Gm-Message-State: AOPr4FXOgVB79LMqmnWUtpbVKsfDpoMcU/TWvvCFaCmNtpiNWTNpgDCBxF1lfxTcaMnXIg== X-Received: by 10.112.126.131 with SMTP id my3mr1095889lbb.74.1462372848258; Wed, 04 May 2016 07:40:48 -0700 (PDT) Received: from [1.0.0.7] ([109.196.196.208]) by smtp.gmail.com with ESMTPSA id uo2sm668879lbb.31.2016.05.04.07.40.46 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 04 May 2016 07:40:46 -0700 (PDT) Subject: Re: Some minor error fixes To: Peter Eisentraut , "pgsql-docs@postgresql.org" References: <571470D8.50907@gmail.com> <88f42cdc-48fe-aeb9-60e7-e27587621a55@2ndquadrant.com> From: Alexander Law Message-ID: <572A09ED.8050204@gmail.com> Date: Wed, 4 May 2016 17:40:45 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: <88f42cdc-48fe-aeb9-60e7-e27587621a55@2ndquadrant.com> Content-Type: multipart/mixed; boundary="------------010604020305040005070604" X-Pg-Spam-Score: 0.6 (/) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-docs Precedence: bulk Sender: pgsql-docs-owner@postgresql.org This is a multi-part message in MIME format. --------------010604020305040005070604 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Hello Peter, Thanks! Please have a look at the some more errors. Regarding second patch, I think, that inconsistency should be fixed by omitting '_name', as this parameter could also include a password. Best regards, Alexander 04.05.2016 04:10, Peter Eisentraut пишет: > On 4/18/16 1:30 AM, Alexander Law wrote: >> Please consider fixing some more minor errors. >> Patches attached. > > fixed > --------------010604020305040005070604 Content-Type: text/x-patch; name="1-fix-ecpg-typos.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="1-fix-ecpg-typos.patch" diff --git a/doc/src/sgml/ecpg.sgml b/doc/src/sgml/ecpg.sgml index 1e285d9..8c0934a 100644 --- a/doc/src/sgml/ecpg.sgml +++ b/doc/src/sgml/ecpg.sgml @@ -6190,7 +6190,7 @@ cc -c test_mod.c -o test_mod.o Next, generate test_cpp.o by compiling - test_cpp.cpp with the C++ compiler:. + test_cpp.cpp with the C++ compiler: c++ -c test_cpp.cpp -o test_cpp.o @@ -7830,7 +7830,7 @@ main(void) this mode is active, it tries to behave as if it were the Informix precompiler for Informix E/SQL. Generally spoken this will allow you to use the dollar sign instead of the EXEC SQL primitive to introduce - embedded SQL commands.: + embedded SQL commands: $int j = 3; $CONNECT TO :dbname; @@ -7902,7 +7902,7 @@ EXEC SQL FETCH MYCUR INTO :userid; This statement closes the current connection. In fact, this is a - synonym for ECPG's DISCONNECT CURRENT.: + synonym for ECPG's DISCONNECT CURRENT: $CLOSE DATABASE; /* close the current connection */ EXEC SQL CLOSE DATABASE; --------------010604020305040005070604 Content-Type: text/x-patch; name="2-fix-ecpg-inconsisteny.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="2-fix-ecpg-inconsisteny.patch" diff --git a/doc/src/sgml/ecpg.sgml b/doc/src/sgml/ecpg.sgml index 8c0934a..35f7f11 100644 --- a/doc/src/sgml/ecpg.sgml +++ b/doc/src/sgml/ecpg.sgml @@ -6296,9 +6296,9 @@ EXEC SQL ALLOCATE DESCRIPTOR mydesc; -CONNECT TO connection_target [ AS connection_name ] [ USER connection_user_name ] +CONNECT TO connection_target [ AS connection_name ] [ USER connection_user ] CONNECT TO DEFAULT -CONNECT connection_user_name +CONNECT connection_user DATABASE connection_target --------------010604020305040005070604 Content-Type: text/x-patch; name="3-fix-pg_xlogdump-typo.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="3-fix-pg_xlogdump-typo.patch" diff --git a/doc/src/sgml/ref/pg_xlogdump.sgml b/doc/src/sgml/ref/pg_xlogdump.sgml index 54ef0a7..445da93 100644 --- a/doc/src/sgml/ref/pg_xlogdump.sgml +++ b/doc/src/sgml/ref/pg_xlogdump.sgml @@ -149,7 +149,7 @@ PostgreSQL documentation - + Timeline from which to read log records. The default is to use the --------------010604020305040005070604 Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs --------------010604020305040005070604--