|From:||Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>|
|To:||Michael Paquier <michael(dot)paquier(at)gmail(dot)com>|
|Cc:||Rushabh Lathia <rushabh(dot)lathia(at)gmail(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>|
|Subject:||Re: pg_dump gets attributes from tables in extensions|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
Michael Paquier wrote:
> On Wed, Feb 25, 2015 at 10:30 AM, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
> > That looks interesting -- I don't recall seeing it. Does it support
> > more doing than one extension? If so, we could certainly integrate it.
> It uses TAP tests to kick pg_dump commands, and I haven't added any logic
> for having more than one extension installed within a single test if that
> is what you mean,
Yeah --- it would be horrible to have modules test_dump1, test_dump2 and
so forth for different details in the extension SQL files.
> but I assume that we could pass to prove_check a variable able to
> install multiple paths and install their content. For now though what
> I have done is adding one line to prove_check to install the content
> of current directory to be able to run TAP tests with one extension.
Haven't looked at the TAP stuff so I have no suggestions.
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
|Next Message||Andreas Karlsson||2015-02-25 04:14:56||Fix autoconf deprecation warnings|
|Previous Message||Michael Paquier||2015-02-25 01:48:12||Re: pg_dump gets attributes from tables in extensions|