From: | Lou Picciano <loupicciano(at)comcast(dot)net> |
---|---|
To: | rajkphb <rajkphbgp(at)gmail(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: postgresql patching |
Date: | 2013-09-10 16:21:40 |
Message-ID: | 342999777.2514295.1378830100085.JavaMail.root@sz0093a.westchester.pa.mail.comcast.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Generally: Because the PostgreSQL coders/fixers/packagers are damn good about integrating needed fixes quickly, to obviate the need for spurious 'field patching'
As an example: http://web.nvd.nist.gov/view/vuln/search-results?query=postgresql&search_type=all&cves=on
Note that the first handful of CVEs listed there are labeled 'pre-' 9.2.4, or 9.1.9. IE, these are remediated in most recent minor revisions of PostgreSQL code.
If you're seeking to make other, 'off-trunk' mods to the code, experts here will chime in...
Lou Picciano
----- Original Message -----
From: rajkphb
To: pgsql-admin(at)postgresql(dot)org
Sent: Tue, 10 Sep 2013 03:17:04 -0000 (UTC)
Subject: [ADMIN] postgresql patching
Hi,
I am relatively new to postgresql. I did not find any detailed documentation on patching .
Please provide me some links where i can get some note on postgresql patching.
Why does postgres documentation does not have patching topic?
Thanks
Suhas
View this message in context: postgresql patching
Sent from the PostgreSQL - admin mailing list archive at Nabble.com.
From | Date | Subject | |
---|---|---|---|
Next Message | Amador Alvarez | 2013-09-10 16:22:35 | Re: postgresql patching |
Previous Message | rajkphb | 2013-09-10 03:17:04 | postgresql patching |