| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Magnus Hagander <magnus(at)hagander(dot)net>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: September 2012 commitfest |
| Date: | 2012-10-11 19:37:00 |
| Message-ID: | CA+U5nMLkck0xsLdL0Ef_nD2M=5+kBx+6Tb-WnG6i7v+PONHANw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 11 October 2012 20:30, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Thu, Oct 11, 2012 at 2:42 PM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
>> I have a quietish few days starting on Saturday, will be looking at this
>> then. Is it only the Windows aspect that needs reviewing? Are we more or
>> less happy with the rest?
>
> I think the Windows issues were the biggest thing, but I suspect there
> may be a few other warts as well. It's a lot of code, and it's
> modifying pg_dump, which is an absolute guarantee that it's built on a
> foundation made out of pure horse manure.
That may be so, but enough people dependent upon it that now I'm
wondering whether we should be looking to create a new utility
altogether, or at least have pg_dump_parallel and pg_dump to avoid any
screw ups with people's backups/restores.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-10-11 19:43:04 | Re: change in LOCK behavior |
| Previous Message | Simon Riggs | 2012-10-11 19:33:55 | Re: change in LOCK behavior |