| From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
|---|---|
| To: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
| Cc: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Use "WAL segment" instead of "log segment" consistently in user-facing messages |
| Date: | 2022-03-31 15:45:56 |
| Message-ID: | 20220331154556.GA199787@nathanxps13 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
At all times, <productname>PostgreSQL</productname> maintains a
<firstterm>write ahead log</firstterm> (WAL) in the <filename>pg_wal/</filename>
- subdirectory of the cluster's data directory. The log records
- every change made to the database's data files. This log exists
+ subdirectory of the cluster's data directory. The WAL records
+ capture every change made to the database's data files. This log exists
I don't think this change really adds anything. The preceding sentence
makes it clear that we are discussing the write-ahead log, and IMO the
change in phrasing ("the log records every change" is changed to "the
records capture every change") subtly changes the meaning of the sentence.
The rest looks good to me.
--
Nathan Bossart
Amazon Web Services: https://aws.amazon.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Julien Rouhaud | 2022-03-31 16:00:36 | Re: Possible fails in pg_stat_statements test |
| Previous Message | Tom Lane | 2022-03-31 15:44:40 | Re: head fails to build on SLES 12 (wal_compression=zstd) |