| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Bossart, Nathan" <bossartn(at)amazon(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_upgrade test chatter |
| Date: | 2021-10-20 02:37:28 |
| Message-ID: | 202110200237.56htdi2lu6s7@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2021-Oct-19, Tom Lane wrote:
> Yeah, my original thought had been to hack this at the test level.
> However, I felt like it'd be worth adding this code because we could
> apply it elsewhere in pg_regress.c to save several psql sessions
> (and hence backend starts) per regression DB creation. That's not a
> huge win, but it'd add up.
Ah, yeah, that sounds like it can be significant under valgrind and
such, so +1.
--
Álvaro Herrera 39°49'30"S 73°17'W — https://www.EnterpriseDB.com/
"Find a bug in a program, and fix it, and the program will work today.
Show the program how to find and fix a bug, and the program
will work forever" (Oliver Silfridge)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2021-10-20 02:41:56 | Re: [RFC] building postgres with meson |
| Previous Message | Tom Lane | 2021-10-20 02:08:52 | Re: pg_upgrade test chatter |