| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: HS locking broken in HEAD |
| Date: | 2013-01-18 17:16:16 |
| Message-ID: | 9577.1358529376@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andres Freund <andres(at)2ndquadrant(dot)com> writes:
> On 2013-01-18 11:16:15 -0500, Tom Lane wrote:
>> I wonder if it'd be practical to, say, run all the contrib regression
>> tests concurrently in different databases of one installation.
> I think it would be a good idea, but I don't immediately have an idea
> how to implement it. It seems to me we would need to put the logic for
> it into pg_regress? Otherwise the lifetime management of the shared
> postmaster seems to get complicated.
Seems like it'd be sufficient to make it work for the "make
installcheck" case, which dodges the postmaster problem.
> What I would really like is to have some basic replication test scenario
> in the regression tests.
Agreed, that's not being tested enough either.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2013-01-18 17:32:53 | Re: logical changeset generation v4 |
| Previous Message | Robert Haas | 2013-01-18 17:14:40 | Re: review: pgbench - aggregation of info written into log |