| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
| Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Re: [COMMITTERS] pgsql: Fix inadequacies in recently added wait events |
| Date: | 2017-08-09 14:14:14 |
| Message-ID: | 23772.1502288054@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> writes:
> As for whether hypothetical check scripts would ever be run, I was
> thinking we should stick them under some make target that developers
> run all the time anyway -- perhaps "check". Shouldn't we catch simple
> mechanically detectable problems as early in the pipeline as possible?
Adding overhead to every developer's every test cycle doesn't sound
like a win. Possibly a reasonable compromise would be to have some
buildfarm members running this check.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2017-08-09 14:51:49 | Re: Re: [COMMITTERS] pgsql: Fix inadequacies in recently added wait events |
| Previous Message | Robert Haas | 2017-08-09 12:14:23 | Re: [COMMITTERS] pgsql: Use MINVALUE/MAXVALUE instead of UNBOUNDED for range partition b |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2017-08-09 14:51:49 | Re: Re: [COMMITTERS] pgsql: Fix inadequacies in recently added wait events |
| Previous Message | Thomas Munro | 2017-08-09 13:39:21 | Re: Partition-wise join for join between (declaratively) partitioned tables |