| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Melanie Plageman <melanieplageman(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Small omission in type_sanity.sql |
| Date: | 2023-03-09 10:45:30 |
| Message-ID: | 20230309104530.xqytfudkd22az6cg@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2023-Jan-27, Andres Freund wrote:
> On 2023-01-27 20:39:04 -0500, Tom Lane wrote:
> > Andres Freund <andres(at)anarazel(dot)de> writes:
> > > Tom, is there a reason we run the various sanity tests early-ish in the
> > > schedule? It does seem to reduce their effectiveness a bit...
> >
> > Originally, those tests were mainly needed to sanity-check the
> > hand-maintained initial catalog data, so it made sense to run them
> > early.
>
> It's also kinda useful to have some basic validity testing early on, because
> if there's something wrong with the catalog values, it'll cause lots of issues
> later.
We can just list the tests twice in the schedule ...
--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Langote | 2023-03-09 10:56:58 | Re: A bug with ExecCheckPermissions |
| Previous Message | Alvaro Herrera | 2023-03-09 10:39:38 | Re: A bug with ExecCheckPermissions |