On Mon, Jul 3, 2017 at 11:00 PM, Tom Lane wrote:
> Michael Paquier writes:
>> On Mon, Jul 3, 2017 at 9:25 PM, Greg Stark wrote:
>>> On 2 July 2017 at 18:33, Tom Lane wrote:
system("cp -a ...") call in favor
Michael Paquier writes:
> On Mon, Jul 3, 2017 at 9:25 PM, Greg Stark wrote:
>> On 2 July 2017 at 18:33, Tom Lane wrote:
>>> system("cp -a ...") call in favor of something more portable.
>> If we're ok with using Perl there's
On Mon, Jul 3, 2017 at 10:02 PM, Alvaro Herrera
wrote:
> Tom Lane wrote:
>
>> (Other unfinished work: teaching the MSVC scripts to use this,
>> and teaching pg_upgrade's test script to use it.)
>
> Maybe it'd be simpler to rewrite pg_upgrade tests using PostgresNode
>
Tom Lane wrote:
> (Other unfinished work: teaching the MSVC scripts to use this,
> and teaching pg_upgrade's test script to use it.)
Maybe it'd be simpler to rewrite pg_upgrade tests using PostgresNode
instead?
--
Álvaro Herrerahttps://www.2ndQuadrant.com/
PostgreSQL
On Mon, Jul 3, 2017 at 9:25 PM, Greg Stark wrote:
> On 2 July 2017 at 18:33, Tom Lane wrote:
>> system("cp -a ...") call in favor of something more portable.
>
> If we're ok with using Perl there's File::Copy::Recursive::dircopy()
> which does exactly that.
On 2 July 2017 at 18:33, Tom Lane wrote:
> system("cp -a ...") call in favor of something more portable.
If we're ok with using Perl there's File::Copy::Recursive::dircopy()
which does exactly that.
--
greg
--
Sent via pgsql-hackers mailing list
Yesterday I spent a bit of time on an idea that we've talked about
before, which is to not run initdb over and over again in contexts like
"make check-world", or even just during "make check" in contrib or in the
recovery or subscription tests. The idea would be to do it once and
then copy the