Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1k9QTe-0004aq-7h for pgsql-docs@arkaria.postgresql.org; Sat, 22 Aug 2020 10:10:22 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1k9QTa-0001Ed-Kl for pgsql-docs@arkaria.postgresql.org; Sat, 22 Aug 2020 10:10:18 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1k9QTa-0001EW-BS for pgsql-docs@lists.postgresql.org; Sat, 22 Aug 2020 10:10:18 +0000 Received: from mail-lf1-x134.google.com ([2a00:1450:4864:20::134]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1k9QTY-0006Xx-2t for pgsql-docs@postgresql.org; Sat, 22 Aug 2020 10:10:17 +0000 Received: by mail-lf1-x134.google.com with SMTP id r25so2104479lfe.5 for ; Sat, 22 Aug 2020 03:10:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=to:from:subject:message-id:date:user-agent:mime-version :content-language; bh=E0SFs9BjLUIJRZPGPVQWuVWb7WQu+y0sgidSkkgCk9w=; b=Snc5nHy1DaoQaCblfXpAhsQ+clx2toE3CHGNWkhpLL4/zIcvWELBDUwv8Tnh5w1xIl IzHKcpMsVORD1K4cXuxIU2aQsKwi5qBNmCAXlzcQm+6u7jK5zBDWLC9kw7bMU496Qvis 1c5boiWhTiw3Xg0rBHtnnbOIW1PLhT2Yt/DJjxHumzztTJ843Upj1wJGFhKxfjvQFzcV 9sgBBFfRYPzZkmnLsUcId+gUqG7z3tlRppbuudZIvaf4c+MbJ5c65Zkj7IGBVk0hVDxs gMp0fvAxqZezELeTZ3xUlYs2Nt0Y2oqqv9wRVEa5dMEFlJl5bnRKp9oTAt45SiGmU/Sj e18g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-language; bh=E0SFs9BjLUIJRZPGPVQWuVWb7WQu+y0sgidSkkgCk9w=; b=cQV6PhlBx74SF8OHgqS6lYHmn7WLJELq9ZDfNzs1qnydy2o6D40dfXtb3dgtC6jvHR iofp3cDkIP1kd6n/7A6CFLBN6xSdx0xUfod6M5qPhNVxXevWhq2OLWaCjVFhVQJKQjm1 XyBL5CDntXmBkk8aw+pugoGfNAiBvkXlNHF4lIGfI99ux8vBUmP1Yw9IBYR6JJygsP+Q yknZ2le2S4MzCYoW/wuU7BSIZRCjbZkLNXTtvHtGcNeiib1pP123poul3Fvh7OfXKyMf V+VN/GstJ4MsydnQFd/Y2pNY9X2DDsOytdQIpwTuP3tJJONGfNUdXHAav3dffbKvFiiK QocA== X-Gm-Message-State: AOAM530pf0TiHeUa3n9uO8eEfMpOoq74dqjog5+csM4LDhQ/urnXHX78 v6323gKfkyvfI7kpACQSGEXfA5HwiRE= X-Google-Smtp-Source: ABdhPJwQ22JYfKh+RPZ9OMX1rB1zILeUDRCrARHznfM9b6B3i2FZ8XKEyuEgMt3RaBpsgJiD/MJmxQ== X-Received: by 2002:a19:cc0f:: with SMTP id c15mr3174495lfg.195.1598091013771; Sat, 22 Aug 2020 03:10:13 -0700 (PDT) Received: from [1.0.0.7] ([178.155.6.252]) by smtp.gmail.com with ESMTPSA id a19sm958821lff.25.2020.08.22.03.10.12 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 22 Aug 2020 03:10:12 -0700 (PDT) To: "pgsql-docs@postgresql.org" From: Alexander Lakhin Subject: Minor fixes for PostgreSQL 13 documentation Message-ID: Date: Sat, 22 Aug 2020 13:10:11 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="------------231BFBFE2DB96D2D7F6B1953" Content-Language: en-US List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk This is a multi-part message in MIME format. --------------231BFBFE2DB96D2D7F6B1953 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Hello, Please consider applying fixes for bugs (incorrect tags, redundant spaces, etc.) I noticed while translating the documentation. Best regards, Alexander --------------231BFBFE2DB96D2D7F6B1953 Content-Type: text/x-patch; charset=UTF-8; name="fix-doc-13-bugs.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="fix-doc-13-bugs.patch" diff --git a/doc/src/sgml/btree.sgml b/doc/src/sgml/btree.sgml index d03ee4d6fa..435b7cb24d 100644 --- a/doc/src/sgml/btree.sgml +++ b/doc/src/sgml/btree.sgml @@ -566,7 +566,7 @@ equalimage(opcintype oid) returns bool options(relopts local_relopts *) returns void - The function is passed a pointer to a local_relopts + The function is passed a pointer to a local_relopts struct, which needs to be filled with a set of operator class specific options. The options can be accessed from other support functions using the PG_HAS_OPCLASS_OPTIONS() and diff --git a/doc/src/sgml/datetime.sgml b/doc/src/sgml/datetime.sgml index bbf50b76f8..d466e09381 100644 --- a/doc/src/sgml/datetime.sgml +++ b/doc/src/sgml/datetime.sgml @@ -564,7 +564,7 @@ - PostgreSQL can accept time zone specifications that + PostgreSQL can accept time zone specifications that are written according to the POSIX standard's rules for the TZ environment variable. POSIX time zone specifications are @@ -635,8 +635,8 @@ or -). The positive sign is used for zones west of Greenwich. (Note that this is the opposite of the ISO-8601 sign convention used elsewhere in - PostgreSQL.) hh can have - one or two digits; mm + PostgreSQL.) hh + can have one or two digits; mm and ss (if used) must have two. diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml index b1c92196e2..800a5414d4 100644 --- a/doc/src/sgml/func.sgml +++ b/doc/src/sgml/func.sgml @@ -9236,7 +9236,7 @@ SELECT EXTRACT(CENTURY FROM TIMESTAMP '2001-02-16 20:38:40'); For timestamp values, the day (of the month) field - (1–31) ; for interval values, the number of days + (1–31); for interval values, the number of days @@ -9460,7 +9460,7 @@ SELECT EXTRACT(MINUTE FROM TIMESTAMP '2001-02-16 20:38:40'); For timestamp values, the number of the month - within the year (1–12) ; for interval values, + within the year (1–12); for interval values, the number of months, modulo 12 (0–11) @@ -14074,7 +14074,7 @@ SELECT xmltable.* size_sq_km float PATH 'SIZE[@unit = "sq_km"]', size_other text PATH 'concat(SIZE[@unit!="sq_km"], " ", SIZE[@unit!="sq_km"]/@unit)', - premier_name text PATH 'PREMIER_NAME' DEFAULT 'not specified') ; + premier_name text PATH 'PREMIER_NAME' DEFAULT 'not specified'); id | ordinality | COUNTRY_NAME | country_id | size_sq_km | size_other | premier_name ----+------------+--------------+------------+------------+--------------+--------------- diff --git a/doc/src/sgml/libpq.sgml b/doc/src/sgml/libpq.sgml index 754581441f..3b954b54a2 100644 --- a/doc/src/sgml/libpq.sgml +++ b/doc/src/sgml/libpq.sgml @@ -781,7 +781,7 @@ PGPing PQping(const char *conninfo); PQsetSSLKeyPassHook_OpenSSL lets an application override - libpq's default + libpq's default handling of encrypted client certificate key files using or interactive prompting. @@ -793,20 +793,23 @@ void PQsetSSLKeyPassHook_OpenSSL(PQsslKeyPassHook_OpenSSL_type hook); int callback_fn(char *buf, int size, PGconn *conn); - which libpq will then call instead of - its default PQdefaultSSLKeyPassHook_OpenSSL handler. The callback - should determine the password for the key and copy it to result-buffer - buf of size size. The string in - buf must be null-terminated. The callback must return the length of - the password stored in buf excluding the null terminator. - On failure, the callback should set buf[0] = '\0' and return 0. - See PQdefaultSSLKeyPassHook_OpenSSL in libpq's - source code for an example. - - + which libpq will then call + instead of its default + PQdefaultSSLKeyPassHook_OpenSSL handler. + The callback should determine the password for the key and copy + it to result-buffer buf of size + size. + The string in buf must be null-terminated. + The callback must return the length of the password stored in + buf excluding the null terminator. + On failure, the callback should set buf[0] = '\0' + and return 0. See PQdefaultSSLKeyPassHook_OpenSSL + in libpq's source code for an example. + + If the user specified an explicit key location, - its path will be in conn->pgsslkey when the callback + its path will be in conn->sslkey when the callback is invoked. This will be empty if the default key path is being used. For keys that are engine specifiers, it is up to engine implementations whether they use the OpenSSL password callback or define their own handling. diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml index 5243f5f346..50f0612b43 100644 --- a/doc/src/sgml/monitoring.sgml +++ b/doc/src/sgml/monitoring.sgml @@ -4440,7 +4440,7 @@ SELECT pid, wait_event_type, wait_event FROM pg_stat_activity WHERE wait_event i name text - name of the SLRU + Name of the SLRU @@ -4644,7 +4644,7 @@ SELECT pid, wait_event_type, wait_event FROM pg_stat_activity WHERE wait_event i argument. The argument can be bgwriter to reset all the counters shown in the pg_stat_bgwriter - view,or archiver to reset all the counters shown in + view, or archiver to reset all the counters shown in the pg_stat_archiver view. @@ -5184,8 +5184,8 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid, finalizing analyze - The command is updating pg_class. When this phase is completed, - ANALYZE will end. + The command is updating pg_class. When this + phase is completed, ANALYZE will end. --------------231BFBFE2DB96D2D7F6B1953--