Tom Lane wrote: > "Massa, Harald Armin" <c...@ghum.de> writes: > > within source code, build options there is: > > - Reserve the shared memory region during backend startup on Windows, > > so that memory allocated by starting third party DLLs doesn't end up > > conflicting with it. Hopefully this solves the long-time issue with > > "could not reattach to shared memory" errors on Win32. > > > I suggest that it should also be pointed out that this fix will be > > backported to 8.3 and 8.4 (as much as I followed the ML); > > Normally, bug fixes that have been back-patched wouldn't be mentioned at > all in a new major release's release notes. The implied base that we > are comparing to in major-release notes is the end of the prior branch's > updates. I'm not sure if this case should be an exception, or if we > should have a different general rule for alpha releases. We'd like to > get more testing on that fix, so I think it is reasonable to mention it > for alpha1 --- but is that an exception specific to this bug fix, or > does it indicate we want to handle bug fixes differently in general > within alpha release notes? > > In any case, it is not the function of the alpha release notes to > discuss changes in earlier release branches. The reason the commit > log points out the back-patch is to make it easier to extract the > information when we prepare release notes for the back-branch updates.
FYI, tools/pgcvslog -d removes backbranch commits automatically. -- Bruce Momjian <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers