From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
---|---|
To: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: initdb recommendations |
Date: | 2019-07-24 19:59:36 |
Message-ID: | 57298c1e-d865-20ff-950c-268439e42ead@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs pgsql-hackers |
On 2019-07-24 16:00, Andrew Dunstan wrote:
> I think we also need to change vcregress.pl to use trust explicitly for
> upgrade checks, just like the Unix upgrade test script does. That should
> help to future-proof us a bit.
Right, I'll add that to my patch.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2019-07-24 20:02:41 | Re: initdb recommendations |
Previous Message | Awad Mackie | 2019-07-24 17:22:35 | Re: REFRESH MATERIALIZED VIEW CONCURRENTLY interaction with ORDER BY |
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2019-07-24 20:02:41 | Re: initdb recommendations |
Previous Message | Fabien COELHO | 2019-07-24 19:41:24 | Re: psql - add SHOW_ALL_RESULTS option |