Marc G. Fournier wrote:
On Wed, 2 Feb 2005, Geoffrey wrote:
Marc G. Fournier wrote:
In order to address a potential security hole recently identified
with the "LOAD" option, the PostgreSQL Global Development Group is
announcing the release of new versions of PostgreSQL going back to
the 7.2.x ve
On Wed, 2 Feb 2005, Geoffrey wrote:
Marc G. Fournier wrote:
In order to address a potential security hole recently identified with the
"LOAD" option, the PostgreSQL Global Development Group is announcing the
release of new versions of PostgreSQL going back to the 7.2.x version.
As always, these
Marc G. Fournier wrote:
In order to address a potential security hole recently identified with
the "LOAD" option, the PostgreSQL Global Development Group is announcing
the release of new versions of PostgreSQL going back to the 7.2.x version.
As always, these releases are available on all mirror
On Wed, 2 Feb 2005, Andrey V. Semyonov wrote:
Marc G. Fournier wrote:
In order to address a potential security hole recently identified with the
"LOAD" option, the PostgreSQL Global Development Group is announcing the
release of new versions of PostgreSQL going back to the 7.2.x version.
As alwa
Marc G. Fournier wrote:
In order to address a potential security hole recently identified with
the "LOAD" option, the PostgreSQL Global Development Group is
announcing the release of new versions of PostgreSQL going back to the
7.2.x version.
As always, these releases are available on all mirro
Geoffrey wrote:
Peter Eisentraut wrote:
Geoffrey wrote:
I want to make sure I understand this post. Does this mean that the
patch will be included in all the source/binaries back to 7.2.x that
are available on the mirrors? Visiting the mirrors, I only see
updates reflected in the v.8.0.1 directory
Peter Eisentraut wrote:
Geoffrey wrote:
I want to make sure I understand this post. Does this mean that the
patch will be included in all the source/binaries back to 7.2.x that
are available on the mirrors? Visiting the mirrors, I only see
updates reflected in the v.8.0.1 directory.
You must be u
Geoffrey wrote:
> I want to make sure I understand this post. Does this mean that the
> patch will be included in all the source/binaries back to 7.2.x that
> are available on the mirrors? Visiting the mirrors, I only see
> updates reflected in the v.8.0.1 directory.
You must be using a broken mi
Marc G. Fournier wrote:
In order to address a potential security hole recently identified with
the "LOAD" option, the PostgreSQL Global Development Group is announcing
the release of new versions of PostgreSQL going back to the 7.2.x version.
I want to make sure I understand this post. Does this
Neil Conway <[EMAIL PROTECTED]> writes:
> On Mon, 2004-10-25 at 00:43, Tom Lane wrote:
>> He's not. There were two other recent security reports, which core kept
>> to ourselves until the release could be made.
> Ah, ok -- fair enough. Are those additional security fixes mentioned in
> the releas
On Mon, 2004-10-25 at 00:43, Tom Lane wrote:
> He's not. There were two other recent security reports, which core kept
> to ourselves until the release could be made.
Ah, ok -- fair enough. Are those additional security fixes mentioned in
the release notes?
-Neil
---(e
Neil Conway <[EMAIL PROTECTED]> writes:
> Marc G. Fournier wrote:
>> In order to address a recent security report from iDefence, we have
>> released 3 new "point" releases: 7.2.6, 7.3.8 and 7.4.6
> Assuming you're referring to the make_oidjoins_check bug,
He's not. There were two other recent s
Marc G. Fournier wrote:
In order to address a recent security report from iDefence, we have
released 3 new "point" releases: 7.2.6, 7.3.8 and 7.4.6
Assuming you're referring to the make_oidjoins_check bug, I don't think
it is accurate to bill these as "security releases". As the 7.4.6
release no
13 matches
Mail list logo
