| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, Bruce Momjian <bruce(at)momjian(dot)us>, Dimitri Fontaine <dfontaine(at)hi-media(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_migrator to /contrib in a later 9.0 beta |
| Date: | 2010-05-01 15:42:14 |
| Message-ID: | 3454.1272728534@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Sat, May 1, 2010 at 3:32 AM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
>> A lot of people are not willing to put stuff labeled "contrib" on
>> their production boxes.
>>
>> And as Tom says, even we *ourselves* acknowledge that things in
>> /contrib are held to a lower standard. If we put that label on
>> pg_migrator, it doesn't exactly signal people that this is something
>> they should use on their critical database.
> Well, I guess that begs the question... IS this something they should
> use on their critical database?
Not unless it gets some serious testing during the 9.0 beta cycle.
Which it surely won't get if it's not included in the core tarball.
I think that having it in contrib for a release cycle or so would be
exactly the right approach, actually. Peter's position that it should
be in /bin is fine *once the bugs are out*. Just dropping it there
doesn't make the bugs go away.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-05-01 16:01:53 | Protecting against case where shmget says EINVAL instead of EEXIST |
| Previous Message | Simon Riggs | 2010-05-01 15:16:47 | Re: standbycheck was:(Re: [HACKERS] testing hot standby |