| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: proposal: separate databases for contrib module testing |
| Date: | 2012-12-02 16:29:44 |
| Message-ID: | 12931.1354465784@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> On 12/02/2012 10:05 AM, Tom Lane wrote:
>> Personally I always thought that was a feature not a bug. If we give
>> each one its own DB, there will be a couple of dozen databases
>> cluttering the installation at the end of "make installcheck", and no
>> convenient way to get rid of them.
> How about if we have a make target to clean these databases out,
> "installcheck-clean", maybe? Alternatively, or in addition, how about if
> we have a separate make target to do things the way I'm suggesting,
> assuming I can make that work?
Either of those would satisfy my concern. The latter might be a bit
easier, not sure.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2012-12-02 17:36:32 | Re: proposal: separate databases for contrib module testing |
| Previous Message | Andrew Dunstan | 2012-12-02 15:42:31 | Re: proposal: separate databases for contrib module testing |