| From: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
|---|---|
| To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | About a recently-added message |
| Date: | 2024-02-14 07:26:52 |
| Message-ID: | 20240214.162652.773291409747353211.horikyota.ntt@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
A recent commit added the following message:
> "wal_level" must be >= logical.
The use of the term "logical" here is a bit confusing, as it's unclear
whether it's meant to be a natural language word or a token. (I
believe it to be a token.)
On the contrary, we already have the following message:
> wal_level must be set to "replica" or "logical" at server start.
This has the conflicting policy about quotation of variable names and
enum values.
I suggest making the quoting policy consistent.
regards.
--
Kyotaro Horiguchi
NTT Open Source Software Center
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrei Lepikhov | 2024-02-14 07:33:39 | Re: Memory consumed by child SpecialJoinInfo in partitionwise join planning |
| Previous Message | Michael Paquier | 2024-02-14 07:23:38 | Re: Parent/child context relation in pg_get_backend_memory_contexts() |