From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
Cc: | pgsql-committers(at)postgresql(dot)org |
Subject: | Re: pgsql: Allow on-the-fly capture of DDL event details |
Date: | 2015-05-12 14:03:40 |
Message-ID: | 20150512140340.GB2523@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Michael Paquier wrote:
> On Tue, May 12, 2015 at 1:05 PM, Alvaro Herrera
> <alvherre(at)2ndquadrant(dot)com> wrote:
> > Sure. I want to avoid doing that, though: we may want to generate a
> > schedule based on src/test/regress/serial_schedule, so that newly added
> > tests to the regular suite are automatically considered by this module.
>
> Mind share more details about that? How would you detect that a given
> test in serial_schedule needs to be considered by test_ddl_deparse
> automatically? WIth a new type of keyword in a schedule file? This
> looks like a different feature to me that's going to need more
> infrastructure...
I was thinking in something simple such as
cat $(srcdir)/src/test/regress/serial_schedule | grep -v tablespace >> the_schedule
> If you want to continue on this way though, I imagine that you will
> need to add a special case in fetchTests of vcregress.pl.
Hrm.
> In any case, it is not good to keep the buildfarm machines broken for
> too long, and personally I would rather avoid adding one more hack in
> the MSVC build scripts.
The MSVC build scripts *are* hacks themselves. Anyway, I'll look into
it.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2015-05-12 14:17:21 | Re: pgsql: Allow on-the-fly capture of DDL event details |
Previous Message | Andrew Dunstan | 2015-05-12 13:42:56 | pgsql: Map basebackup tablespaces using a tablespace_map file |