From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
---|---|
To: | Stephen Frost <sfrost(at)snowman(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Re: [COMMITTERS] pgsql: Improve pg_dump regression tests and code coverage |
Date: | 2017-03-20 13:07:39 |
Message-ID: | 9f69774d-efee-f22b-200f-758aadd0d5f0@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
On 3/20/17 08:33, Stephen Frost wrote:
>> So was this 3340 line patch posted or discussed anyplace before it got
>> committed?
> I've mentioned a few times that I'm working on improving pg_dump
> regression tests and code coverage, which is what these were. I'm a bit
> surprised that it's, apparently, a surprise to anyone or that strictly
> adding regression tests in the existing framework deserves very much
> discussion.
I think we had this discussion about adding a large number of (pg_dump)
tests without discussion or review already about a year ago, so I for
one am surprised that are still surprised.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2017-03-20 13:11:52 | Re: Re: [COMMITTERS] pgsql: Improve pg_dump regression tests and code coverage |
Previous Message | Robert Haas | 2017-03-20 13:07:06 | Re: [COMMITTERS] pgsql: Improve pg_dump regression tests and code coverage |
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2017-03-20 13:11:52 | Re: Re: [COMMITTERS] pgsql: Improve pg_dump regression tests and code coverage |
Previous Message | Robert Haas | 2017-03-20 13:07:06 | Re: [COMMITTERS] pgsql: Improve pg_dump regression tests and code coverage |