| From: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
|---|---|
| To: | "Abraham, Danny" <danny_abraham(at)bmc(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Identify release contents |
| Date: | 2011-07-19 12:41:38 |
| Message-ID: | 4E257B82.20803@postnewspapers.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 19/07/2011 6:48 PM, Abraham, Danny wrote:
> I can tell for sure, reading the release notes that it is fixed for
> 8.2.18, 8.3.8 and 8.4.1.
The fix should be in 9.0 too. It might not appear in the 9.0 release
notes explicitly if 9.0 was branched off after the 8.4.1 release,
because then 9.0 would inherit all changes from 8.4.1.
I haven't verified if that's the case, but I haven't seen any "cannot
reattach to shared memory" errors reported here for some time, nor have
I had any on 9.0 during any of my Windows-based testing.
If you want to be totally 100% certain you can trace the fix to exactly
where it was applied in 9.0, check the revision history in git. See
http://git.postgresql.org/ .
--
Craig Ringer
POST Newspapers
276 Onslow Rd, Shenton Park
Ph: 08 9381 3088 Fax: 08 9388 2258
ABN: 50 008 917 717
http://www.postnewspapers.com.au/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | dennis jenkins | 2011-07-19 12:56:11 | Re: Detecting memory leaks with libpq? |
| Previous Message | Abraham, Danny | 2011-07-19 10:48:57 | Identify release contents |