| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp>, coelho(at)cri(dot)ensmp(dot)fr, rafia(dot)sabih(at)enterprisedb(dot)com, michael(dot)paquier(at)gmail(dot)com, Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp, robertmhaas(at)gmail(dot)com, pavel(dot)stehule(at)gmail(dot)com, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: pgbench - allow to store select results into variables |
| Date: | 2017-04-06 00:28:24 |
| Message-ID: | 20170406002824.rr6xrdwzkkorrxto@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2017-04-05 20:24:19 -0400, Tom Lane wrote:
> Having said all that, I think we're at the point in the commitfest
> where if there's any design question at all about a patch, it should
> get booted to the next cycle. We are going to have more than enough
> to do to stabilize what's already committed, we don't need to be
> adding more uncertainty.
+1
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuo Ishii | 2017-04-06 00:36:50 | Re: pgbench - allow to store select results into variables |
| Previous Message | Tom Lane | 2017-04-06 00:24:19 | Re: pgbench - allow to store select results into variables |