| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: should we enable log_checkpoints out of the box? |
| Date: | 2021-11-04 15:04:58 |
| Message-ID: | CA+TgmoZOD9VUn57vMNxcjqcxEwgyyLCUwRs=-rTgqh7iM5rXzw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Nov 4, 2021 at 10:59 AM Bharath Rupireddy
<bharath(dot)rupireddyforpostgres(at)gmail(dot)com> wrote:
> With log_checkpoints=on, the "./initdb -D data" generates few
> checkpoints logs [1]. I hope this is okay as it's a one-time thing per
> database cluster. Thoughts?
I think you should arrange to suppress that output. There's no reason
why initdb can't pass -c log_checkpoints=off. See backend_options in
initdb.c.
I didn't spot any other problems on a quick read-through.
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrey Borodin | 2021-11-04 15:52:22 | Re: Why doesn't GiST VACUUM require a super-exclusive lock, like nbtree VACUUM? |
| Previous Message | Robert Haas | 2021-11-04 15:01:26 | Re: Automatic notification of top transaction IDs |