On Thu, Jun 10, 2010 at 9:46 AM, Paul Baker wrote:
>
> All,
>
> I received this question from a customer yesterday (below), and unfortunately
> I do not have the answer. Please let us know if you know the answer, it
> would be greatly appreciated...
>
> "What we are trying to figure out is if r
On Thu, Jun 10, 2010 at 3:29 PM, John R Pierce wrote:
> Scott Marlowe wrote:
>>
>> On Thu, Jun 10, 2010 at 2:35 PM, John R Pierce
>> wrote:
>>
>>>
>>> It appears (using the public Sunsolve patchfinder) that the newest
>>> version
>>> of PostgreSQL 8.3 that Sun has a patch for is 8.3.9 (138826-06
Scott Marlowe wrote:
On Thu, Jun 10, 2010 at 2:35 PM, John R Pierce wrote:
It appears (using the public Sunsolve patchfinder) that the newest version
of PostgreSQL 8.3 that Sun has a patch for is 8.3.9 (138826-06 or
138827-06), while 8.3.11 has been out for about a month now, and fixes
thes
Paul Baker wrote:
All,
I received this question from a customer yesterday (below), and unfortunately I
do not have the answer. Please let us know if you know the answer, it would be
greatly appreciated...
"What we are trying to figure out is if removing the packages SUNWpostgr-83-devel, SUN
On Thu, Jun 10, 2010 at 2:35 PM, John R Pierce wrote:
> It appears (using the public Sunsolve patchfinder) that the newest version
> of PostgreSQL 8.3 that Sun has a patch for is 8.3.9 (138826-06 or
> 138827-06), while 8.3.11 has been out for about a month now, and fixes
> these CVEs.
Note that
All,
I received this question from a customer yesterday (below), and unfortunately I do not have the answer. Please let us know if you know the answer, it would be greatly appreciated...
"What we are trying to figure out is if removing the packages SUNWpostgr-83-devel, SUNWpostgr-83-pl, SUN
