Thread: Changelog version from 8.1.2 to 9.3.6
Dear All,
Thanks for your support.
Could you please assist for changelog version option used to find the differences between the versions.
In addition we required information of changes done in all releases from 8.1.2 to 9.3.6.
Thanks in advance .
Regards,
Yogesh
Hi Yogesh,
   here
https://www.postgresql.org/docs/9.3/static/release.html
you can find all release notes, including changelogs for all
versions.
HTH,
Moreno.
Il 10/06/2016 13:17, Yogesh Sharma ha scritto:
<blockquote
cite="mid:8F86F8F397DDD345B25EA2EF3E21648299B36A78@EXCH-MB03-U2.nectechnologies.in"
type="cite">
<meta name="Generator" content="Microsoft Word 14 (filtered
medium)">
<!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
-->
<blockquote style="border:none;border-left:solid #CCCCCC
1.0pt;padding:0in 0in 0in
6.0pt;margin-left:4.8pt;margin-right:0in">
<span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Dear
All,
<span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Â
<span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Thanks
for your support.
<span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Â
<span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Could
you please assist for changelog version option used to
find the differences between the versions.
<span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">In
addition  we required information of changes done in
all releases from 8.1.2 to 9.3.6.
<span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Â
<span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Thanks
in advance .
<span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Â
<span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Regards,
<span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Yogesh
On 06/10/2016 04:23 AM, Moreno Andreo wrote: > Hi Yogesh, > here > > https://www.postgresql.org/docs/9.3/static/release.html > > you can find all release notes, including changelogs for all versions. Also a one page version: https://bucardo.org/postgres_all_versions.html > > HTH, > Moreno. > > Il 10/06/2016 13:17, Yogesh Sharma ha scritto: >> >> Dear All, >> >> >> >> Thanks for your support. >> >> >> >> Could you please assist for changelog version option used to find >> the differences between the versions. >> >> In addition we required information of changes done in all >> releases from 8.1.2 to 9.3.6. >> >> >> >> Thanks in advance . >> >> >> >> Regards, >> >> Yogesh >> > -- Adrian Klaver adrian.klaver@aklaver.com
Dear All, Thanks in advance. I have doubt regarding release notes of all versions. As per release notes, below change logs are mentioned in all versions. "(8.3.8,8.4.1,8.2.14) Make LOAD of an already-loaded loadable module into a no-op (Tom Lane)" 1. What is meaning of above lines? 2. This changes are implemented only in above versions or is it propagated on every above newer versions after that? 3. Why same line is mentioned in the release notes of above 8.3.8,8.4.1,8.2.14 versions? Regards, Yogesh -----Original Message----- From: pgsql-general-owner@postgresql.org [mailto:pgsql-general-owner@postgresql.org] On Behalf Of Adrian Klaver Sent: Friday, June 10, 2016 6:47 PM To: Moreno Andreo; pgsql-general@postgresql.org Subject: Re: [GENERAL] Changelog version from 8.1.2 to 9.3.6 On 06/10/2016 04:23 AM, Moreno Andreo wrote: > Hi Yogesh, > here > > https://www.postgresql.org/docs/9.3/static/release.html > > you can find all release notes, including changelogs for all versions. Also a one page version: https://bucardo.org/postgres_all_versions.html > > HTH, > Moreno. > > Il 10/06/2016 13:17, Yogesh Sharma ha scritto: >> >> Dear All, >> >> >> >> Thanks for your support. >> >> >> >> Could you please assist for changelog version option used to find >> the differences between the versions. >> >> In addition we required information of changes done in all >> releases from 8.1.2 to 9.3.6. >> >> >> >> Thanks in advance . >> >> >> >> Regards, >> >> Yogesh >> > -- Adrian Klaver adrian.klaver@aklaver.com -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Yogesh Sharma wrote: > I have doubt regarding release notes of all versions. > As per release notes, below change logs are mentioned in all versions. > > "(8.3.8,8.4.1,8.2.14) Make LOAD of an already-loaded loadable module into a no-op (Tom Lane)" > 1. What is meaning of above lines? > 2. This changes are implemented only in above versions or is it propagated on every above newer > versions after that? > 3. Why same line is mentioned in the release notes of above 8.3.8,8.4.1,8.2.14 versions? Ad 1: As of the cited versions, nothing will be done if you use LOAD to load a module that is already loaded. Ad 2: The change was a bugfix that was applied to the development version (so it is included in 9.0 and later) and was backpatched to 8.2, 8.3 and 8.4. If you want to know details about a change like this, you'll have to dig into the git logs and possibly the code. The commit was 602a9ef5a7c60151e10293ae3c4bb3fbb0132d03 in master, 57710f39cc55cba1e98c718300a811aadacec7c5 in 8.4, 5927d9f642c4cf6233e5fedd3468087995c00523 in 8.3 and 22f77b0f9db1220789b262cda6dccad49d031643 in 8.2. Ad 3: Because the same fix was applied to these three versions. It is safe to assume that a problem that was fixed in 8.4 will also be fixed in 9.0 and above, even though the 9.0 release notes don't explicitly mention it - they mostly contain new features. When reading up on the changes between 8.1.2 and 9.3.6 (a daunting task) you can usually limit yourself to reading 8.2, 8.3, 8.4, 9.0, 9.1, 9.2 and 9.3. This should cover all behaviour changes that are likely to affect you. The minor releases should not change behaviour other than fixing bugs. Yours, Laurenz Albe
Yogesh Sharma wrote:
> I have doubt regarding release notes of all versions.
> As per release notes, below change logs are mentioned in all versions.
>
> "(8.3.8,8.4.1,8.2.14) Make LOAD of an already-loaded loadable module into a no-op (Tom Lane)"
> 1. What is meaning of above lines?
> 2. This changes are implemented only in above versions or is it propagated on every above newer
> versions after that?
> 3. Why same line is mentioned in the release notes of above 8.3.8,8.4.1,8.2.14 versions?
Ad 1:
As of the cited versions, nothing will be done if you use LOAD to load a module
that is already loaded.
Ad 2:
The change was a bugfix that was applied to the development version (so it is included
in 9.0 and later) and was backpatched to 8.2, 8.3 and 8.4.
> 8.2, 8.3, and 8.4 are all Major releases of the PostgreSQL product. For > most other products it would as if the numbering went from "15, to 16, to > 17". The last 8.x release was 8.4 (so, there were 5 major releases that all > shared the same prefix value of 8) and the 9.x series goes from 9.0 to 9.6 > (presently in beta). Instead of 9.7 we will be going to 10.0 AND at the > same time modernizing our numbering scheme to lose the prefix-suffix > components. IOW, after 10.0 the next major release will be 11.0. The .0 > will increment for minor releases in which we only apply bug-fixes. There > will no longer be a third number. Currently are minor upgrades reversible, that is, can we rollback from 9.4.3 to 9.4.2.
> 8.2, 8.3, and 8.4 are all Major releases of the PostgreSQL product. For
> most other products it would as if the numbering went from "15, to 16, to
> 17". The last 8.x release was 8.4 (so, there were 5 major releases that all
> shared the same prefix value of 8) and the 9.x series goes from 9.0 to 9.6
> (presently in beta). Instead of 9.7 we will be going to 10.0 AND at the
> same time modernizing our numbering scheme to lose the prefix-suffix
> components. IOW, after 10.0 the next major release will be 11.0. The .0
> will increment for minor releases in which we only apply bug-fixes. There
> will no longer be a third number.
Currently are minor upgrades reversible, that is, can we rollback from
9.4.3 to 9.4.2.
Dear David sir/All,
Thanks for your help.
Just wanted to confirm few things.
(9.3.5,9.2.9,9.1.14,9.0.18,8.4.22) Fix REASSIGN OWNED to not fail for text search objects (Álvaro Herrera)
As per my understanding from what you told the fix was done in 9.3.5 and then back patched to all the remaining version mentioned above.
My concern is why it was back patched to these particular version only.
Also will these feature be available only in these particular version and above 9.3.5 version or is it available in all the version above 8.4.22
This is not about this particular patch, I want to understand the multiple version number which are mentioned before several patch at given link.
https://bucardo.org/postgres_all_versions.html
Please let me know what yours thought onto this.
Regards,
Yogesh
From: David G. Johnston [mailto:david.g.johnston@gmail.com]
Sent: Wednesday, June 15, 2016 7:18 PM
To: Albe Laurenz
Cc: Yogesh Sharma; Adrian Klaver; Moreno Andreo; pgsql-general@postgresql.org
Subject: Re: [GENERAL] Changelog version from 8.1.2 to 9.3.6
On Wed, Jun 15, 2016 at 3:31 AM, Albe Laurenz <laurenz.albe@wien.gv.at> wrote:
Yogesh Sharma wrote:
> I have doubt regarding release notes of all versions.
> As per release notes, below change logs are mentioned in all versions.
>
> "(8.3.8,8.4.1,8.2.14) Make LOAD of an already-loaded loadable module into a no-op (Tom Lane)"
> 1. What is meaning of above lines?
> 2. This changes are implemented only in above versions or is it propagated on every above newer
> versions after that?
> 3. Why same line is mentioned in the release notes of above 8.3.8,8.4.1,8.2.14 versions?
Ad 1:
As of the cited versions, nothing will be done if you use LOAD to load a module
that is already loaded.
Ad 2:
The change was a bugfix that was applied to the development version (so it is included
in 9.0 and later) and was backpatched to 8.2, 8.3 and 8.4.
Just to be totally clear on this point.
8.2, 8.3, and 8.4 are all Major releases of the PostgreSQL product. For most other products it would as if the numbering went from "15, to 16, to 17". The last 8.x release was 8.4 (so, there were 5 major releases that all shared the same prefix value of 8) and the 9.x series goes from 9.0 to 9.6 (presently in beta). Instead of 9.7 we will be going to 10.0 AND at the same time modernizing our numbering scheme to lose the prefix-suffix components. IOW, after 10.0 the next major release will be 11.0. The .0 will increment for minor releases in which we only apply bug-fixes. There will no longer be a third number.
The rest of Albe's comments apply and are largely driven by this structure. Each major-release is considered stand-alone and so if the same basic change is made to more than one major release all of them will have it documented. But only the initial introduction or application of the change is documented - any subsequent major or minor release has that behavior unless a new release note indicates that said behavior changed again.
David J.
Please don't top post. On Thursday, June 16, 2016 3:42:53 AM EDT Yogesh Sharma wrote: > Dear David sir/All, > > Thanks for your help. > Just wanted to confirm few things. > > (9.3.5,9.2.9,9.1.14,9.0.18,8.4.22) Fix REASSIGN OWNED to not fail for text > search objects (Álvaro Herrera) > As per my understanding from what you told the fix was done in 9.3.5 and > then back patched to all the remaining version mentioned above. My concern > is why it was back patched to these particular version only. Also will > these feature be available only in these particular version and above 9.3.5 > version or is it available in all the version above 8.4.22 It's available in 9.3.x with x >= 5, 9.2.x with x >= 9, 9.1.x with x >= 14, 9.0.x with x >= 18, and 8.4.x with x >= 22. And in 9.4.x and 9.5.x for all x. > This is not about this particular patch, I want to understand the multiple > version number which are mentioned before several patch at given link. > https://bucardo.org/postgres_all_versions.html > > Please let me know what yours thought onto this. > > > Regards, > Yogesh >
Dear David sir/All,
Thanks for your help.
Just wanted to confirm few things.
(9.3.5,9.2.9,9.1.14,9.0.18,8.4.22) Fix REASSIGN OWNED to not fail for text search objects (Álvaro Herrera)
As per my understanding from what you told the fix was done in 9.3.5 and then back patched to all the remaining version mentioned above.
My concern is why it was back patched to these particular version only.