pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
postgresql 11 release notes
8+ messages / 3 participants
[nested] [flat]

Commits from this thread:
  2018-06-23 2d502b8128  doc:  update PG 11 release notes, mostly typo fixes
* postgresql 11 release notes
@ 2018-06-14 23:13  Brad DeJong <bpd0018@gmail.com>
  0 siblings, 1 reply; 8+ messages in thread

From: Brad DeJong @ 2018-06-14 23:13 UTC (permalink / raw)
  To: pgsql-docs@lists.postgresql.org

The diff is for release-11.sgml.

I fixed typos and grammar + rephrased some things that didn't seem to flow

The only major change is the section on PSQL_PAGER.

In the section on the new --create-slot option for pg_basebackup, it seems
like <option>--slot</option> should include the =slotname part but I don't
know the DocBook markup for that (maybe <replaceable>?).

I did not build the documentation after making my changes so the patch
definitely needs to be sanity checked.

Thanks.

Attachments:

release-11.diff (application/octet-stream, 7.3K) download diff --git a/doc/src/sgml/release-11.sgml b/doc/src/sgml/release-11.sgml index 7599c6f..037ff9c 100644 --- a/doc/src/sgml/release-11.sgml +++ b/doc/src/sgml/release-11.sgml @@ -629,7 +629,7 @@ Branch: master [6bdf1303b] Avoid wrong results for power() with NaN </para> <para> - This features is disabled by default + This feature is disabled by default but can be enabled by changing <link linkend="guc-enable-partitionwise-join"><varname>enable_partitionwise_join</varname></link>. </para> @@ -647,7 +647,7 @@ Branch: master [6bdf1303b] Avoid wrong results for power() with NaN </para> <para> - This features is disabled by default + This feature is disabled by default but can be enabled by changing <link linkend="guc-enable-partitionwise-aggregate"><varname>enable_partitionwise_aggregate</varname></link>. </para> @@ -1159,8 +1159,8 @@ same commits as above --> <para> - Add <link - linkend="pg-stat-activity-view"><structname>pg_stat_activity</structname>.<structfield>backend_type</structfield></link> + <link linkend="pg-stat-activity-view"><structname>pg_stat_activity</structname>. + <structfield>backend_type</structfield></link> now shows the type of background worker (Peter Eisentraut) </para> @@ -1315,7 +1315,7 @@ same commits as above --> <para> - Add default roles which controls file system access (Stephen Frost) + Add default roles which control file system access (Stephen Frost) </para> <para> @@ -1364,7 +1364,7 @@ same commits as above </para> <para> - Previously super users were exclusively granted to access these + Previously, super-users were exclusively granted access to these functions. </para> @@ -1424,7 +1424,7 @@ same commits as above <para> Add server setting <link linkend="guc-ssl-passphrase-command"><varname>ssl_passphrase_command</varname></link> - to allow supplying of the the passphrase for <acronym>SSL</acronym> + to allow supplying of the passphrase for <acronym>SSL</acronym> key files (Peter Eisentraut) </para> @@ -1467,7 +1467,7 @@ same commits as above <para> The new unit is "B". This is in addition to "kB", "MB", "GB" - and "TB", which were accepted previously. + and "TB", which are already allowed. </para> </listitem> @@ -1567,7 +1567,7 @@ same commits as above --> <para> - Exclude unlogged, temporary tables, and + Exclude unlogged, temporary tables and <filename>pg_internal.init</filename> files from streaming base backups (David Steele) </para> @@ -1595,7 +1595,7 @@ same commits as above <para> Allow replication slots to be advanced programatically, rather - than be consumed by subscribers (Petr Jelinek) + than being consumed by subscribers (Petr Jelinek) </para> <para> @@ -1726,8 +1726,8 @@ same commits as above <para> Also, if any table mentioned in <command>VACUUM</command> uses - a column list, then <command>ANALYZE</command> keyword must be - supplied; previously <command>ANALYZE</command> was implied in + a column list, then the <command>ANALYZE</command> keyword must be + supplied. Previously, <command>ANALYZE</command> was implied in such cases. </para> </listitem> @@ -1760,7 +1760,7 @@ same commits as above </para> <para> - This is useful for allowing aggregate functions be optimized and + This is useful for allowing aggregate functions to be optimized and to work as window functions. </para> @@ -1803,7 +1803,7 @@ same commits as above </para> <para> - Also allow PL/PL/Perl, PL/Python, and PL/Tcl to handle + Also allow PL/Perl, PL/Python, and PL/Tcl to handle composite-domain function arguments and results. Also improve PL/Python domain handling. </para> @@ -1896,7 +1896,7 @@ same commits as above <para> Add text search function <link linkend="textsearch-functions-table"><function>websearch_to_tsquery()</function></link> - that supports a queries syntax similar to that used by web search + that supports a query syntax similar to that used by web search engines (Victor Drobny, Dmitry Ivanov) </para> </listitem> @@ -1909,7 +1909,7 @@ same commits as above <para> Add function <link linkend="textsearch-functions-table"><function>json(b)_to_tsvector()</function></link> - to create text search query for matching + to create a text search query for matching <type>JSON</type>/<type>JSONB </type>values (Dmitry Dolgov) </para> @@ -2144,10 +2144,13 @@ same commits as above </para> <para> - This allows <application>psql</application>'s default pager to - be specified as a separate environment variable from the pager - for other applications. <envar>PAGER</envar> is still honored - if <envar>PSQL_PAGER</envar> is not set. + In addition to <application>psql</application>, other applications + use the <envar>PAGER</envar> environment variable. Having + <envar>PSQL_PAGER</envar> as a separate environment variable allows + you to use one pager for those applications and a different pager + for <application>psql</application>. <application>psql</application> + will still honor <envar>PAGER</envar> if <envar>PSQL_PAGER</envar> + is not set. </para> </listitem> @@ -2309,7 +2312,7 @@ same commits as above --> <para> - Add approximated Zipfian-distributed random generator to + Add an approximated Zipfian-distributed random generator to <application>pgbench</application> (Alik Khilazhev) </para> </listitem> @@ -2379,16 +2382,16 @@ same commits as above --> <para> - Add <link + Add an option to <link linkend="app-pgbasebackup"><application>pg_basebackup</application></link> - option to create a named replication slot (Michael Banck) + that creates a named replication slot (Michael Banck) </para> <para> The option <option>--create-slot</option> creates the named replication slot (<option>--slot</option>) when the <acronym>WAL</acronym> streaming method - (<option>-wal-method=stream</option>) is used. + (<option>--wal-method=stream</option>) is used. </para> <para> @@ -2560,7 +2563,7 @@ same commits as above </para> <para> - This is useful if the system to be loaded has a different collation + This is useful if the system to be loaded has different collation definitions or endianness, requiring the rows to be stored in different partitions. </para> @@ -2572,7 +2575,7 @@ same commits as above --> <para> - Add ability to suppress dumping and restoring of comments + Add an option to suppress dumping and restoring of comments (Robins Tharakan) </para>
^ permalink raw reply [nested|flat] 8+ messages in thread

* Re: postgresql 11 release notes
@ 2018-06-15 10:58  Brad DeJong <bpd0018@gmail.com>
  parent: Brad DeJong <bpd0018@gmail.com>
  0 siblings, 1 reply; 8+ messages in thread

From: Brad DeJong @ 2018-06-15 10:58 UTC (permalink / raw)
  To: pgsql-docs@lists.postgresql.org

same patch but renamed to match the patch file naming convention

On Thu, Jun 14, 2018 at 6:13 PM, Brad DeJong <bpd0018@gmail.com> wrote:

> The diff is for release-11.sgml.
>
> I fixed typos and grammar + rephrased some things that didn't seem to flow
>
> The only major change is the section on PSQL_PAGER.
>
> In the section on the new --create-slot option for pg_basebackup, it seems
> like <option>--slot</option> should include the =slotname part but I don't
> know the DocBook markup for that (maybe <replaceable>?).
>
> I did not build the documentation after making my changes so the patch
> definitely needs to be sanity checked.
>
> Thanks.
>
>
>

Attachments:

release-11-v1.patch (application/octet-stream, 7.3K) download diff --git a/doc/src/sgml/release-11.sgml b/doc/src/sgml/release-11.sgml index 7599c6f..037ff9c 100644 --- a/doc/src/sgml/release-11.sgml +++ b/doc/src/sgml/release-11.sgml @@ -629,7 +629,7 @@ Branch: master [6bdf1303b] Avoid wrong results for power() with NaN </para> <para> - This features is disabled by default + This feature is disabled by default but can be enabled by changing <link linkend="guc-enable-partitionwise-join"><varname>enable_partitionwise_join</varname></link>. </para> @@ -647,7 +647,7 @@ Branch: master [6bdf1303b] Avoid wrong results for power() with NaN </para> <para> - This features is disabled by default + This feature is disabled by default but can be enabled by changing <link linkend="guc-enable-partitionwise-aggregate"><varname>enable_partitionwise_aggregate</varname></link>. </para> @@ -1159,8 +1159,8 @@ same commits as above --> <para> - Add <link - linkend="pg-stat-activity-view"><structname>pg_stat_activity</structname>.<structfield>backend_type</structfield></link> + <link linkend="pg-stat-activity-view"><structname>pg_stat_activity</structname>. + <structfield>backend_type</structfield></link> now shows the type of background worker (Peter Eisentraut) </para> @@ -1315,7 +1315,7 @@ same commits as above --> <para> - Add default roles which controls file system access (Stephen Frost) + Add default roles which control file system access (Stephen Frost) </para> <para> @@ -1364,7 +1364,7 @@ same commits as above </para> <para> - Previously super users were exclusively granted to access these + Previously, super-users were exclusively granted access to these functions. </para> @@ -1424,7 +1424,7 @@ same commits as above <para> Add server setting <link linkend="guc-ssl-passphrase-command"><varname>ssl_passphrase_command</varname></link> - to allow supplying of the the passphrase for <acronym>SSL</acronym> + to allow supplying of the passphrase for <acronym>SSL</acronym> key files (Peter Eisentraut) </para> @@ -1467,7 +1467,7 @@ same commits as above <para> The new unit is "B". This is in addition to "kB", "MB", "GB" - and "TB", which were accepted previously. + and "TB", which are already allowed. </para> </listitem> @@ -1567,7 +1567,7 @@ same commits as above --> <para> - Exclude unlogged, temporary tables, and + Exclude unlogged, temporary tables and <filename>pg_internal.init</filename> files from streaming base backups (David Steele) </para> @@ -1595,7 +1595,7 @@ same commits as above <para> Allow replication slots to be advanced programatically, rather - than be consumed by subscribers (Petr Jelinek) + than being consumed by subscribers (Petr Jelinek) </para> <para> @@ -1726,8 +1726,8 @@ same commits as above <para> Also, if any table mentioned in <command>VACUUM</command> uses - a column list, then <command>ANALYZE</command> keyword must be - supplied; previously <command>ANALYZE</command> was implied in + a column list, then the <command>ANALYZE</command> keyword must be + supplied. Previously, <command>ANALYZE</command> was implied in such cases. </para> </listitem> @@ -1760,7 +1760,7 @@ same commits as above </para> <para> - This is useful for allowing aggregate functions be optimized and + This is useful for allowing aggregate functions to be optimized and to work as window functions. </para> @@ -1803,7 +1803,7 @@ same commits as above </para> <para> - Also allow PL/PL/Perl, PL/Python, and PL/Tcl to handle + Also allow PL/Perl, PL/Python, and PL/Tcl to handle composite-domain function arguments and results. Also improve PL/Python domain handling. </para> @@ -1896,7 +1896,7 @@ same commits as above <para> Add text search function <link linkend="textsearch-functions-table"><function>websearch_to_tsquery()</function></link> - that supports a queries syntax similar to that used by web search + that supports a query syntax similar to that used by web search engines (Victor Drobny, Dmitry Ivanov) </para> </listitem> @@ -1909,7 +1909,7 @@ same commits as above <para> Add function <link linkend="textsearch-functions-table"><function>json(b)_to_tsvector()</function></link> - to create text search query for matching + to create a text search query for matching <type>JSON</type>/<type>JSONB </type>values (Dmitry Dolgov) </para> @@ -2144,10 +2144,13 @@ same commits as above </para> <para> - This allows <application>psql</application>'s default pager to - be specified as a separate environment variable from the pager - for other applications. <envar>PAGER</envar> is still honored - if <envar>PSQL_PAGER</envar> is not set. + In addition to <application>psql</application>, other applications + use the <envar>PAGER</envar> environment variable. Having + <envar>PSQL_PAGER</envar> as a separate environment variable allows + you to use one pager for those applications and a different pager + for <application>psql</application>. <application>psql</application> + will still honor <envar>PAGER</envar> if <envar>PSQL_PAGER</envar> + is not set. </para> </listitem> @@ -2309,7 +2312,7 @@ same commits as above --> <para> - Add approximated Zipfian-distributed random generator to + Add an approximated Zipfian-distributed random generator to <application>pgbench</application> (Alik Khilazhev) </para> </listitem> @@ -2379,16 +2382,16 @@ same commits as above --> <para> - Add <link + Add an option to <link linkend="app-pgbasebackup"><application>pg_basebackup</application></link> - option to create a named replication slot (Michael Banck) + that creates a named replication slot (Michael Banck) </para> <para> The option <option>--create-slot</option> creates the named replication slot (<option>--slot</option>) when the <acronym>WAL</acronym> streaming method - (<option>-wal-method=stream</option>) is used. + (<option>--wal-method=stream</option>) is used. </para> <para> @@ -2560,7 +2563,7 @@ same commits as above </para> <para> - This is useful if the system to be loaded has a different collation + This is useful if the system to be loaded has different collation definitions or endianness, requiring the rows to be stored in different partitions. </para> @@ -2572,7 +2575,7 @@ same commits as above --> <para> - Add ability to suppress dumping and restoring of comments + Add an option to suppress dumping and restoring of comments (Robins Tharakan) </para>
^ permalink raw reply [nested|flat] 8+ messages in thread

* Re: postgresql 11 release notes
@ 2018-06-19 18:39  Euler Taveira <euler@timbira.com.br>
  parent: Brad DeJong <bpd0018@gmail.com>
  0 siblings, 1 reply; 8+ messages in thread

From: Euler Taveira @ 2018-06-19 18:39 UTC (permalink / raw)
  To: Brad DeJong <bpd0018@gmail.com>; +Cc: pgsql-docs@lists.postgresql.org

2018-06-15 7:58 GMT-03:00 Brad DeJong <bpd0018@gmail.com>:
> same patch but renamed to match the patch file naming convention
>
Comments above:

        <para>
-        Previously super users were exclusively granted to access these
+        Previously, super-users were exclusively granted access to these
         functions.
        </para>

The terminology used in the documentation is "superuser".

        <para>
         The new unit is "B".  This is in addition to "kB", "MB", "GB"
-        and "TB", which were accepted previously.
+        and "TB", which are already allowed.
        </para>

I would replace only "were" by "are": "which are accepted previously".

        <para>
-        Exclude unlogged, temporary tables, and
+        Exclude unlogged, temporary tables and
         <filename>pg_internal.init</filename> files from streaming base
         backups (David Steele)
        </para>

AFAIK postgres uses Oxford comma a lot.

        <para>
         Also, if any table mentioned in <command>VACUUM</command> uses
-        a column list, then <command>ANALYZE</command> keyword must be
-        supplied;  previously <command>ANALYZE</command> was implied in
+        a column list, then the <command>ANALYZE</command> keyword must be
+        supplied. Previously, <command>ANALYZE</command> was implied in
         such cases.
        </para>

I prefer to maintain semicolon and add a comma after "previously".

        <para>
-        This allows <application>psql</application>'s default pager to
-        be specified as a separate environment variable from the pager
-        for other applications.  <envar>PAGER</envar> is still honored
-        if <envar>PSQL_PAGER</envar> is not set.
+        In addition to <application>psql</application>, other applications
+        use the <envar>PAGER</envar> environment variable. Having
+        <envar>PSQL_PAGER</envar> as a separate environment variable allows
+        you to use one pager for those applications and a different pager
+        for <application>psql</application>. <application>psql</application>
+        will still honor <envar>PAGER</envar> if <envar>PSQL_PAGER</envar>
+        is not set.
        </para>

I don't see this as an improvement.

        <para>
-        Add ability to suppress dumping and restoring of comments
+        Add an option to suppress dumping and restoring of comments
         (Robins Tharakan)
        </para>

I would suggest "Add an option to suppress dumping and restoring comments".


-- 
   Euler Taveira                                   Timbira -
http://www.timbira.com.br/
   PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento




^ permalink  raw  reply  [nested|flat] 8+ messages in thread

* Re: postgresql 11 release notes
@ 2018-06-20 02:20  Euler Taveira <euler@timbira.com.br>
  parent: Euler Taveira <euler@timbira.com.br>
  0 siblings, 1 reply; 8+ messages in thread

From: Euler Taveira @ 2018-06-20 02:20 UTC (permalink / raw)
  To: Brad DeJong <bpd0018@gmail.com>; +Cc: pgsql-docs@lists.postgresql.org

Brad, your forgot to reply to pgsql-docs.

2018-06-19 20:21 GMT-03:00 Brad DeJong <bpd0018@gmail.com>:
> How about dropping the which clause entirely? I split this off as
> release-11-newunit-v1.patch for further discussion.
>
Works for me. Could you append it to v2?

>>         <para>
>> -        Exclude unlogged, temporary tables, and
>> +        Exclude unlogged, temporary tables and
>>          <filename>pg_internal.init</filename> files from streaming base
>>          backups (David Steele)
>>         </para>
>>
>> AFAIK postgres uses Oxford comma a lot.
>
> I left this change in the v2 patch.
> I didn't remove it because it was an Oxford comma; I removed it because
> there are only two items, tables and files, so this should not be a comma
> separated list.
> Unlogged and temporary both modify tables and tell us what kind of tables
> are being excluded.
> If this was a list, the items should be semi-colon separated because of the
> comma between unlogged and temporary.
> For example - Exclude unlogged, temporary tables; b-tree indexes; and
> pg_internal.init files from streaming base backups.
>
I see. I think the sentence should be "Exclude unlogged tables,
temporary tables, and <filename>pg_internal.init</filename> files from
streaming base backups".


-- 
   Euler Taveira                                   Timbira -
http://www.timbira.com.br/
   PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento




^ permalink  raw  reply  [nested|flat] 8+ messages in thread

* Re: postgresql 11 release notes
@ 2018-06-21 10:08  Brad DeJong <bpd0018@gmail.com>
  parent: Euler Taveira <euler@timbira.com.br>
  0 siblings, 2 replies; 8+ messages in thread

From: Brad DeJong @ 2018-06-21 10:08 UTC (permalink / raw)
  To: Euler Taveira <euler@timbira.com.br>; +Cc: pgsql-docs@lists.postgresql.org

On Tue, Jun 19, 2018 at 9:20 PM, Euler Taveira <euler@timbira.com.br> wrote:

> Brad, your forgot to reply to pgsql-docs.
>
> 2018-06-19 20:21 GMT-03:00 Brad DeJong <bpd0018@gmail.com>:
> > How about dropping the which clause entirely? I split this off as
> > release-11-newunit-v1.patch for further discussion.
> >
> Works for me. Could you append it to v2?
>
> Done.

> >>         <para>
> >> -        Exclude unlogged, temporary tables, and
> >> +        Exclude unlogged, temporary tables and
> >>          <filename>pg_internal.init</filename> files from streaming
> base
> >>          backups (David Steele)
> >>         </para>
> >>
> >> AFAIK postgres uses Oxford comma a lot.
> >
> > I left this change in the v2 patch.
> > I didn't remove it because it was an Oxford comma; I removed it because
> > there are only two items, tables and files, so this should not be a comma
> > separated list.
> > Unlogged and temporary both modify tables and tell us what kind of tables
> > are being excluded.
> > If this was a list, the items should be semi-colon separated because of
> the
> > comma between unlogged and temporary.
> > For example - Exclude unlogged, temporary tables; b-tree indexes; and
> > pg_internal.init files from streaming base backups.
> >
> I see. I think the sentence should be "Exclude unlogged tables,
> temporary tables, and <filename>pg_internal.init</filename> files from
> streaming base backups".
>
> I like it. Done.

>
> --
>    Euler Taveira                                   Timbira -
> http://www.timbira.com.br/
>    PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
>

Attachments:

release-11-v3.patch (application/octet-stream, 8.1K) download diff --git a/doc/src/sgml/release-11.sgml b/doc/src/sgml/release-11.sgml index 7599c6f..6f3429f 100644 --- a/doc/src/sgml/release-11.sgml +++ b/doc/src/sgml/release-11.sgml @@ -629,7 +629,7 @@ Branch: master [6bdf1303b] Avoid wrong results for power() with NaN </para> <para> - This features is disabled by default + This feature is disabled by default but can be enabled by changing <link linkend="guc-enable-partitionwise-join"><varname>enable_partitionwise_join</varname></link>. </para> @@ -647,7 +647,7 @@ Branch: master [6bdf1303b] Avoid wrong results for power() with NaN </para> <para> - This features is disabled by default + This feature is disabled by default but can be enabled by changing <link linkend="guc-enable-partitionwise-aggregate"><varname>enable_partitionwise_aggregate</varname></link>. </para> @@ -1159,8 +1159,8 @@ same commits as above --> <para> - Add <link - linkend="pg-stat-activity-view"><structname>pg_stat_activity</structname>.<structfield>backend_type</structfield></link> + <link linkend="pg-stat-activity-view"><structname>pg_stat_activity</structname>. + <structfield>backend_type</structfield></link> now shows the type of background worker (Peter Eisentraut) </para> @@ -1315,7 +1315,7 @@ same commits as above --> <para> - Add default roles which controls file system access (Stephen Frost) + Add default roles which control file system access (Stephen Frost) </para> <para> @@ -1325,7 +1325,7 @@ same commits as above <literal>pg_execute_server_program</literal>. These roles now also control who can use <command>COPY</command> and extension <link linkend="file-fdw"><application>file_fdw</application></link>. - Previously only super-users could use these functions, and that + Previously only superusers could use these functions, and that is still the default behavior. </para> </listitem> @@ -1338,7 +1338,7 @@ same commits as above <para> Allow access to file system functions to be controlled by <command>GRANT</command>/<command>REVOKE</command> permissions, - rather than super-user checks (Stephen Frost) + rather than superuser checks (Stephen Frost) </para> <para> @@ -1364,7 +1364,7 @@ same commits as above </para> <para> - Previously super users were exclusively granted to access these + Previously, superusers were exclusively granted access to these functions. </para> @@ -1387,10 +1387,10 @@ same commits as above </para> <para> - <productname>PostgreSQL</productname> only allows super-users to + <productname>PostgreSQL</productname> only allows superusers to access <application>postgres_fdw</application> tables without passwords, e.g. via <literal>peer</literal>. Previously the - session owner had to be a super-user to allow such access; now + session owner had to be a superuser to allow such access; now the view owner is checked instead. </para> </listitem> @@ -1424,7 +1424,7 @@ same commits as above <para> Add server setting <link linkend="guc-ssl-passphrase-command"><varname>ssl_passphrase_command</varname></link> - to allow supplying of the the passphrase for <acronym>SSL</acronym> + to allow supplying of the passphrase for <acronym>SSL</acronym> key files (Peter Eisentraut) </para> @@ -1467,7 +1467,7 @@ same commits as above <para> The new unit is "B". This is in addition to "kB", "MB", "GB" - and "TB", which were accepted previously. + and "TB". </para> </listitem> @@ -1567,7 +1567,7 @@ same commits as above --> <para> - Exclude unlogged, temporary tables, and + Exclude unlogged tables, temporary tables, and <filename>pg_internal.init</filename> files from streaming base backups (David Steele) </para> @@ -1595,7 +1595,7 @@ same commits as above <para> Allow replication slots to be advanced programatically, rather - than be consumed by subscribers (Petr Jelinek) + than being consumed by subscribers (Petr Jelinek) </para> <para> @@ -1726,8 +1726,8 @@ same commits as above <para> Also, if any table mentioned in <command>VACUUM</command> uses - a column list, then <command>ANALYZE</command> keyword must be - supplied; previously <command>ANALYZE</command> was implied in + a column list, then the <command>ANALYZE</command> keyword must be + supplied; previously, <command>ANALYZE</command> was implied in such cases. </para> </listitem> @@ -1760,7 +1760,7 @@ same commits as above </para> <para> - This is useful for allowing aggregate functions be optimized and + This is useful for allowing aggregate functions to be optimized and to work as window functions. </para> @@ -1803,7 +1803,7 @@ same commits as above </para> <para> - Also allow PL/PL/Perl, PL/Python, and PL/Tcl to handle + Also allow PL/Perl, PL/Python, and PL/Tcl to handle composite-domain function arguments and results. Also improve PL/Python domain handling. </para> @@ -1896,7 +1896,7 @@ same commits as above <para> Add text search function <link linkend="textsearch-functions-table"><function>websearch_to_tsquery()</function></link> - that supports a queries syntax similar to that used by web search + that supports a query syntax similar to that used by web search engines (Victor Drobny, Dmitry Ivanov) </para> </listitem> @@ -1909,7 +1909,7 @@ same commits as above <para> Add function <link linkend="textsearch-functions-table"><function>json(b)_to_tsvector()</function></link> - to create text search query for matching + to create a text search query for matching <type>JSON</type>/<type>JSONB </type>values (Dmitry Dolgov) </para> @@ -2309,7 +2309,7 @@ same commits as above --> <para> - Add approximated Zipfian-distributed random generator to + Add an approximated Zipfian-distributed random generator to <application>pgbench</application> (Alik Khilazhev) </para> </listitem> @@ -2379,16 +2379,16 @@ same commits as above --> <para> - Add <link + Add an option to <link linkend="app-pgbasebackup"><application>pg_basebackup</application></link> - option to create a named replication slot (Michael Banck) + that creates a named replication slot (Michael Banck) </para> <para> The option <option>--create-slot</option> creates the named replication slot (<option>--slot</option>) when the <acronym>WAL</acronym> streaming method - (<option>-wal-method=stream</option>) is used. + (<option>--wal-method=stream</option>) is used. </para> <para> @@ -2560,7 +2560,7 @@ same commits as above </para> <para> - This is useful if the system to be loaded has a different collation + This is useful if the system to be loaded has different collation definitions or endianness, requiring the rows to be stored in different partitions. </para> @@ -2572,7 +2572,7 @@ same commits as above --> <para> - Add ability to suppress dumping and restoring of comments + Add an option to suppress dumping and restoring comments (Robins Tharakan) </para> @@ -2884,7 +2884,7 @@ same commits as above </para> <para> - Previously only super-users could call adminpack functions; + Previously only superusers could call adminpack functions; now role permissions are checked. </para> </listitem>
^ permalink raw reply [nested|flat] 8+ messages in thread

* Re: postgresql 11 release notes
@ 2018-06-21 11:01  Brad DeJong <bpd0018@gmail.com>
  parent: Brad DeJong <bpd0018@gmail.com>
  1 sibling, 1 reply; 8+ messages in thread

From: Brad DeJong @ 2018-06-21 11:01 UTC (permalink / raw)
  To: Euler Taveira <euler@timbira.com.br>; +Cc: pgsql-docs@lists.postgresql.org

On Thu, Jun 21, 2018 at 5:08 AM, Brad DeJong <bpd0018@gmail.com> wrote:

>
>
> On Tue, Jun 19, 2018 at 9:20 PM, Euler Taveira <euler@timbira.com.br>
> wrote:
>>
>> I see. I think the sentence should be "Exclude unlogged tables,
>> temporary tables, and <filename>pg_internal.init</filename> files from
>> streaming base backups".
>>
>> I like it. Done.
>
>>
>>
Just to make the difference explicit

"Exclude unlogged, temporary tables and ..."
=> if (table.unlogged == true AND table.temporary == true) then exclude
table

"Exclude unlogged tables, temporary tables, and ..."
=> if (table.unlogged == true OR table.temporary == true) then exclude table

I do not know whether the condition is an AND or an OR.
When you said "I think the sentence should be ...", I took that to mean
that you know that the condition should be an OR.

^ permalink  raw  reply  [nested|flat] 8+ messages in thread

* Re: postgresql 11 release notes
@ 2018-06-22 20:52  Euler Taveira <euler@timbira.com.br>
  parent: Brad DeJong <bpd0018@gmail.com>
  0 siblings, 0 replies; 8+ messages in thread

From: Euler Taveira @ 2018-06-22 20:52 UTC (permalink / raw)
  To: Brad DeJong <bpd0018@gmail.com>; +Cc: pgsql-docs@lists.postgresql.org

2018-06-21 8:01 GMT-03:00 Brad DeJong <bpd0018@gmail.com>:
> When you said "I think the sentence should be ...", I took that to mean that
> you know that the condition should be an OR.
>
There are separate conditions in the code (each one was done in
separate commits).


-- 
   Euler Taveira                                   Timbira -
http://www.timbira.com.br/
   PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento




^ permalink  raw  reply  [nested|flat] 8+ messages in thread

* Re: postgresql 11 release notes
@ 2018-06-23 21:24  Bruce Momjian <bruce@momjian.us>
  parent: Brad DeJong <bpd0018@gmail.com>
  1 sibling, 0 replies; 8+ messages in thread

From: Bruce Momjian @ 2018-06-23 21:24 UTC (permalink / raw)
  To: Brad DeJong <bpd0018@gmail.com>; +Cc: Euler Taveira <euler@timbira.com.br>; pgsql-docs@lists.postgresql.org

On Thu, Jun 21, 2018 at 05:08:39AM -0500, Brad DeJong wrote:
> On Tue, Jun 19, 2018 at 9:20 PM, Euler Taveira <euler@timbira.com.br> wrote:
>     > I left this change in the v2 patch.
>     > I didn't remove it because it was an Oxford comma; I removed it because
>     > there are only two items, tables and files, so this should not be a comma
>     > separated list.
>     > Unlogged and temporary both modify tables and tell us what kind of tables
>     > are being excluded.
>     > If this was a list, the items should be semi-colon separated because of
>     the
>     > comma between unlogged and temporary.
>     > For example - Exclude unlogged, temporary tables; b-tree indexes; and
>     > pg_internal.init files from streaming base backups.
>     >
>     I see. I think the sentence should be "Exclude unlogged tables,
>     temporary tables, and <filename>pg_internal.init</filename> files from
>     streaming base backups".
> 
> 
> I like it. Done. 

Patch applied.  This was a great help, thanks.  The "This features" typo
was already found.  I did not apply this part since it would have added
whitespace after the period.

> -        Add <link
> -        linkend="pg-stat-activity-view"><structname>pg_stat_activity</structname>.<structfield>backend_type</structfield></link>
> +        <link linkend="pg-stat-activity-view"><structname>pg_stat_activity</structname>.
> +        <structfield>backend_type</structfield></link>

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

+ As you are, so once was I.  As I am, so you will be. +
+                      Ancient Roman grave inscription +




^ permalink  raw  reply  [nested|flat] 8+ messages in thread


end of thread, other threads:[~2018-06-23 21:24 UTC | newest]

Thread overview: 8+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2018-06-14 23:13 postgresql 11 release notes Brad DeJong <bpd0018@gmail.com>
2018-06-15 10:58 ` Brad DeJong <bpd0018@gmail.com>
2018-06-19 18:39   ` Euler Taveira <euler@timbira.com.br>
2018-06-20 02:20     ` Euler Taveira <euler@timbira.com.br>
2018-06-21 10:08       ` Brad DeJong <bpd0018@gmail.com>
2018-06-21 11:01         ` Brad DeJong <bpd0018@gmail.com>
2018-06-22 20:52           ` Euler Taveira <euler@timbira.com.br>
2018-06-23 21:24         ` Bruce Momjian <bruce@momjian.us>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox