| From: | David Fetter <david(at)fetter(dot)org> |
|---|---|
| To: | Adam Berlin <aberlin(at)pivotal(dot)io> |
| Cc: | Dmitry Dolgov <9erthalion6(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: C testing for Postgres |
| Date: | 2019-06-28 21:54:44 |
| Message-ID: | 20190628215444.GD20338@fetter.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jun 28, 2019 at 09:42:54AM -0400, Adam Berlin wrote:
> Here are my takeaways from the previous discussions:
>
> * there *is* interest in testing
Yep.
> * we shouldn't take it too far
> * there are already tests being written under `src/test/modules`, but
> without a consistent way of describing expectations and displaying results
This is a giant problem.
> * no tool was chosen
If there's a way to get this in the tree, assuming people agree it
should be there, that'd be fantastic.
Our current system has been creaking for years.
Best,
David.
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778
Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-06-28 22:05:57 | Re: BUG #15383: Join Filter cost estimation problem in 10.5 |
| Previous Message | David Steele | 2019-06-28 21:47:20 | Re: Commitfest 2019-07, the first of five* for PostgreSQL 13 |