From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Josh Berkus <josh(at)agliodbs(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Brad Nicholson <bnichols(at)ca(dot)afilias(dot)info>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_migrator issue with contrib |
Date: | 2009-06-08 03:36:46 |
Message-ID: | 200906080336.n583akJ25787@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Robert Haas wrote:
> OK, that's more or less what I thought, and what I intended to convey
> upthread. As far as core Postgres is concerned this is a new feature,
> and we haven't worked out all the kinks yet. As long as we set
> expectations accordingly, I think that's OK. You mention CVEs for
> these contrib issues, but will CVEs still be issued if we make clear
> that this is experimental only? I would hope not, since that would
> amount to a policy that any half-baked code anywhere on pgfoundry is
> just as much our responsibility as core Postgres. Surely we're
> allowed to say "good progress has been made here, but we harbor no
> illusions that it's bullet-proof."
Again, there is nothing pg_migrator-specific about these security
issues.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2009-06-08 03:50:17 | Re: pg_migrator issue with contrib |
Previous Message | Bruce Momjian | 2009-06-08 03:36:00 | Re: pg_migrator issue with contrib |