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@momjian.us> http://momjian.us EnterpriseDB
http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
