| From: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: check-world has suddenly started spewing stuff on stderr |
| Date: | 2022-02-16 20:17:10 |
| Message-ID: | c43dfe23-6e80-31ee-a9ed-9f60f7903837@iki.fi |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 16/02/2022 19:04, Tom Lane wrote:
> $ make check-world >/dev/null
> 2022-02-16 11:57:47.548 EST [3339702] LOG: database system was not properly shut down; automatic recovery in progress
> 2022-02-16 11:57:47.612 EST [3339713] LOG: database system was not properly shut down; automatic recovery in progress
> 2022-02-16 11:57:59.379 EST [3345366] LOG: database system was not properly shut down; automatic recovery in progress
> 2022-02-16 11:57:59.445 EST [3345429] LOG: database system was not properly shut down; automatic recovery in progress
>
> Whoever is responsible for that, please fix it.
That's on me. 'initdb' started to print those after the xlog.c splitting
patch.
Something went wrong in bootstrapping apparently. I'll investigate tomorrow.
- Heikki
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2022-02-16 20:21:31 | Re: do only critical work during single-user vacuum? |
| Previous Message | Matthias van de Meent | 2022-02-16 20:14:16 | Re: Lowering the ever-growing heap->pd_lower |