PG 12 draft release notes

classic Classic list List threaded Threaded
14 messages Options
Reply | Threaded
Open this post in threaded view
|

PG 12 draft release notes

Bruce Momjian
I have posted a draft copy of the PG 12 release notes here:

        http://momjian.us/pgsql_docs/release-12.html

They are committed to git.  It includes links to the main docs, where
appropriate.  Our official developer docs will rebuild in a few hours.

--
  Bruce Momjian  <[hidden email]>        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 +


Reply | Threaded
Open this post in threaded view
|

Re: PG 12 draft release notes

Oleg Bartunov-3
Bruce,

I noticed that jsonpath in your version is mentioned only in functions
chapter, but  commit
72b6460336e86ad5cafd3426af6013c7d8457367 is about implementation of
SQL-2016 standard. We implemented JSON Path language as a jsonpath
datatype with a bunch of support functions, our implementation
supports 14 out of 15 features and it's the most complete
implementation (we compared oracle, mysql and ms sql).

On Sat, May 11, 2019 at 11:33 PM Bruce Momjian <[hidden email]> wrote:

>
> I have posted a draft copy of the PG 12 release notes here:
>
>         http://momjian.us/pgsql_docs/release-12.html
>
> They are committed to git.  It includes links to the main docs, where
> appropriate.  Our official developer docs will rebuild in a few hours.
>
> --
>   Bruce Momjian  <[hidden email]>        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 +
>
>


--
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company


Reply | Threaded
Open this post in threaded view
|

Re: PG 12 draft release notes

Bruce Momjian
On Sun, May 12, 2019 at 10:00:38AM +0300, Oleg Bartunov wrote:
> Bruce,
>
> I noticed that jsonpath in your version is mentioned only in functions
> chapter, but  commit
> 72b6460336e86ad5cafd3426af6013c7d8457367 is about implementation of
> SQL-2016 standard. We implemented JSON Path language as a jsonpath
> datatype with a bunch of support functions, our implementation
> supports 14 out of 15 features and it's the most complete
> implementation (we compared oracle, mysql and ms sql).

Glad you asked.  I was very confused about why a data type was added for
a new path syntax.  Is it a new storage format for JSON, or something
else?  I need help on this.

--
  Bruce Momjian  <[hidden email]>        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 +


Reply | Threaded
Open this post in threaded view
|

Re: PG 12 draft release notes

Jonathan S. Katz-3
In reply to this post by Bruce Momjian
Hi Bruce,

On 5/11/19 4:33 PM, Bruce Momjian wrote:
> I have posted a draft copy of the PG 12 release notes here:
>
> http://momjian.us/pgsql_docs/release-12.html
>
> They are committed to git.  It includes links to the main docs, where
> appropriate.  Our official developer docs will rebuild in a few hours.

Thank you for working on this, I know it's a gargantuan task.

I have a small modification for a section entitled "Source Code" which
is a repeat of the previous section. Based on the bullet points in that
part, I thought "Documentation" might be a more appropriate name; please
see attached.

Thanks,

Jonathan

release.patch (550 bytes) Download Attachment
signature.asc (849 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: PG 12 draft release notes

David Rowley-3
In reply to this post by Bruce Momjian
On Sun, 12 May 2019 at 08:33, Bruce Momjian <[hidden email]> wrote:
>
> I have posted a draft copy of the PG 12 release notes here:
>
>         http://momjian.us/pgsql_docs/release-12.html

I noticed a couple of different spellings of Álvaro's name.  Loading
the file line by line into a table and crudely performing:

select distinct name from (select
trim(regexp_split_to_table(substring(a, '\((.*?)\)'),',')) as name
from r where a like '%(%)%')a order by name;

turned up variations in Michaël and Pavel's names

The attached fixes.

--
 David Rowley                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

normalise_release_note_names.patch (11K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: PG 12 draft release notes

Bruce Momjian
In reply to this post by Jonathan S. Katz-3
On Sun, May 12, 2019 at 10:49:07AM -0400, Jonathan Katz wrote:

> Hi Bruce,
>
> On 5/11/19 4:33 PM, Bruce Momjian wrote:
> > I have posted a draft copy of the PG 12 release notes here:
> >
> > http://momjian.us/pgsql_docs/release-12.html
> >
> > They are committed to git.  It includes links to the main docs, where
> > appropriate.  Our official developer docs will rebuild in a few hours.
>
> Thank you for working on this, I know it's a gargantuan task.
>
> I have a small modification for a section entitled "Source Code" which
> is a repeat of the previous section. Based on the bullet points in that
> part, I thought "Documentation" might be a more appropriate name; please
> see attached.

Yes, I saw that myself and just updated it.  Thanks.

---------------------------------------------------------------------------


>
> Thanks,
>
> Jonathan

> diff --git a/doc/src/sgml/release-12.sgml b/doc/src/sgml/release-12.sgml
> index 5f5d1da33d..1bbd91a02e 100644
> --- a/doc/src/sgml/release-12.sgml
> +++ b/doc/src/sgml/release-12.sgml
> @@ -2617,7 +2617,7 @@ Require a C99-supported compiler, and <acronym>MSCV</acronym> 2013 or later on <
>     </sect3>
>  
>     <sect3>
> -    <title>Source Code</title>
> +    <title>Documentation</title>
>  
>       <itemizedlist>
>  





--
  Bruce Momjian  <[hidden email]>        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 +


Reply | Threaded
Open this post in threaded view
|

Re: PG 12 draft release notes

Bruce Momjian
In reply to this post by Bruce Momjian
On Sun, May 12, 2019 at 09:49:40AM -0400, Bruce Momjian wrote:

> On Sun, May 12, 2019 at 10:00:38AM +0300, Oleg Bartunov wrote:
> > Bruce,
> >
> > I noticed that jsonpath in your version is mentioned only in functions
> > chapter, but  commit
> > 72b6460336e86ad5cafd3426af6013c7d8457367 is about implementation of
> > SQL-2016 standard. We implemented JSON Path language as a jsonpath
> > datatype with a bunch of support functions, our implementation
> > supports 14 out of 15 features and it's the most complete
> > implementation (we compared oracle, mysql and ms sql).
>
> Glad you asked.  I was very confused about why a data type was added for
> a new path syntax.  Is it a new storage format for JSON, or something
> else?  I need help on this.

I talked to Alexander Korotkov on chat about this.  The data types are
used as arguments to the functions, similar to how tsquery and tsvector
are used for full text search.

Therefore, the data types are not really useful on their own, but as
support for path functions.  However, path functions are more like JSON
queries, rather than traditional functions, so it odd to list them under
functions, but there isn't a more reasonable place to put them.

Alexander researched how we listed full text search in the release notes
that added the feature, but we had  "General" category at that time that
we don't have now.

--
  Bruce Momjian  <[hidden email]>        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 +


Reply | Threaded
Open this post in threaded view
|

Re: PG 12 draft release notes

Bruce Momjian
In reply to this post by David Rowley-3
On Mon, May 13, 2019 at 01:37:25PM +1200, David Rowley wrote:

> On Sun, 12 May 2019 at 08:33, Bruce Momjian <[hidden email]> wrote:
> >
> > I have posted a draft copy of the PG 12 release notes here:
> >
> >         http://momjian.us/pgsql_docs/release-12.html
>
> I noticed a couple of different spellings of Álvaro's name.  Loading
> the file line by line into a table and crudely performing:
>
> select distinct name from (select
> trim(regexp_split_to_table(substring(a, '\((.*?)\)'),',')) as name
> from r where a like '%(%)%')a order by name;
>
> turned up variations in Michaël and Pavel's names

That is a big help, thanks, applied.

--
  Bruce Momjian  <[hidden email]>        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 +


Reply | Threaded
Open this post in threaded view
|

Re: PG 12 draft release notes

Fabien COELHO-3
In reply to this post by Bruce Momjian

Hello Bruce,

> I have posted a draft copy of the PG 12 release notes here:
>
> http://momjian.us/pgsql_docs/release-12.html
>
> They are committed to git.  It includes links to the main docs, where
> appropriate.  Our official developer docs will rebuild in a few hours.

Pgbench entry "Improve pgbench error reporting with clearer messages and
return codes" is by Peter Eisentraut, not me. I just reviewed it.

--
Fabien.


Reply | Threaded
Open this post in threaded view
|

Re: PG 12 draft release notes

Oleg Bartunov-3
In reply to this post by Bruce Momjian
On Mon, May 13, 2019 at 6:52 AM Bruce Momjian <[hidden email]> wrote:

>
> On Sun, May 12, 2019 at 09:49:40AM -0400, Bruce Momjian wrote:
> > On Sun, May 12, 2019 at 10:00:38AM +0300, Oleg Bartunov wrote:
> > > Bruce,
> > >
> > > I noticed that jsonpath in your version is mentioned only in functions
> > > chapter, but  commit
> > > 72b6460336e86ad5cafd3426af6013c7d8457367 is about implementation of
> > > SQL-2016 standard. We implemented JSON Path language as a jsonpath
> > > datatype with a bunch of support functions, our implementation
> > > supports 14 out of 15 features and it's the most complete
> > > implementation (we compared oracle, mysql and ms sql).
> >
> > Glad you asked.  I was very confused about why a data type was added for
> > a new path syntax.  Is it a new storage format for JSON, or something
> > else?  I need help on this.
>
> I talked to Alexander Korotkov on chat about this.  The data types are
> used as arguments to the functions, similar to how tsquery and tsvector
> are used for full text search.
>
> Therefore, the data types are not really useful on their own, but as
> support for path functions.  However, path functions are more like JSON
> queries, rather than traditional functions, so it odd to list them under
> functions, but there isn't a more reasonable place to put them.
>
> Alexander researched how we listed full text search in the release notes
> that added the feature, but we had  "General" category at that time that
> we don't have now.
I attached slide about our Jsonpath implementation in Postgres, it
summarizes the reasons to have jsonpath data type. But my point was:
JSON Path is a part of SQL-2016 standard and I think it's worth to
mention it, not just a set of jsonb functions.

>
> --
>   Bruce Momjian  <[hidden email]>        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 +



--
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company

Screenshot 2019-05-13 at 10.04.21.png (76K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: PG 12 draft release notes

Bruce Momjian
In reply to this post by Fabien COELHO-3
On Mon, May 13, 2019 at 08:41:25AM +0200, Fabien COELHO wrote:

>
> Hello Bruce,
>
> > I have posted a draft copy of the PG 12 release notes here:
> >
> > http://momjian.us/pgsql_docs/release-12.html
> >
> > They are committed to git.  It includes links to the main docs, where
> > appropriate.  Our official developer docs will rebuild in a few hours.
>
> Pgbench entry "Improve pgbench error reporting with clearer messages and
> return codes" is by Peter Eisentraut, not me. I just reviewed it.

Thanks, fixed.

--
  Bruce Momjian  <[hidden email]>        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 +


Reply | Threaded
Open this post in threaded view
|

Re: PG 12 draft release notes

Bruce Momjian
In reply to this post by Oleg Bartunov-3
On Mon, May 13, 2019 at 10:08:57AM +0300, Oleg Bartunov wrote:

> On Mon, May 13, 2019 at 6:52 AM Bruce Momjian <[hidden email]> wrote:
> >
> > On Sun, May 12, 2019 at 09:49:40AM -0400, Bruce Momjian wrote:
> > > On Sun, May 12, 2019 at 10:00:38AM +0300, Oleg Bartunov wrote:
> > > > Bruce,
> > > >
> > > > I noticed that jsonpath in your version is mentioned only in functions
> > > > chapter, but  commit
> > > > 72b6460336e86ad5cafd3426af6013c7d8457367 is about implementation of
> > > > SQL-2016 standard. We implemented JSON Path language as a jsonpath
> > > > datatype with a bunch of support functions, our implementation
> > > > supports 14 out of 15 features and it's the most complete
> > > > implementation (we compared oracle, mysql and ms sql).
> > >
> > > Glad you asked.  I was very confused about why a data type was added for
> > > a new path syntax.  Is it a new storage format for JSON, or something
> > > else?  I need help on this.
> >
> > I talked to Alexander Korotkov on chat about this.  The data types are
> > used as arguments to the functions, similar to how tsquery and tsvector
> > are used for full text search.
> >
> > Therefore, the data types are not really useful on their own, but as
> > support for path functions.  However, path functions are more like JSON
> > queries, rather than traditional functions, so it odd to list them under
> > functions, but there isn't a more reasonable place to put them.
> >
> > Alexander researched how we listed full text search in the release notes
> > that added the feature, but we had  "General" category at that time that
> > we don't have now.
>
> I attached slide about our Jsonpath implementation in Postgres, it
> summarizes the reasons to have jsonpath data type. But my point was:
> JSON Path is a part of SQL-2016 standard and I think it's worth to
> mention it, not just a set of jsonb functions.

So, are you suggesting we mention the jsonpath data type in the Data
Type section, even though it is useless without jsonpath, which is in
another section, or are you suggesting to move the jsonpath item to the
Data Type section?

--
  Bruce Momjian  <[hidden email]>        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 +


Reply | Threaded
Open this post in threaded view
|

Re: PG 12 draft release notes

nickb
In reply to this post by Bruce Momjian
On Sat, May 11, 2019, at 22:33, Bruce Momjian wrote:
> http://momjian.us/pgsql_docs/release-12.html

There is a typo in E.1.3.1.1.:
> Expressions are evaluated at table partitioned table creation time.
First "table" seems to be excessive.

Regards,
Nick.


Reply | Threaded
Open this post in threaded view
|

Re: PG 12 draft release notes

Bruce Momjian
On Tue, May 14, 2019 at 11:53:23AM +0200, nickb wrote:
> On Sat, May 11, 2019, at 22:33, Bruce Momjian wrote:
> > http://momjian.us/pgsql_docs/release-12.html
>
> There is a typo in E.1.3.1.1.:
> > Expressions are evaluated at table partitioned table creation time.
> First "table" seems to be excessive.

Yep, fixed, thanks.

--
  Bruce Momjian  <[hidden email]>        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 +