Comment typo in xlogutils.c

Started by Masahiko Sawadaover 8 years ago2 messages
#1Masahiko Sawada
sawada.mshk@gmail.com
1 attachment(s)

Hi,

Attached patch for $subject.

s/apruptly/abruptly

Regards,

--
Masahiko Sawada
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center

Attachments:

fix_typo_in_xlogutils_c.patchapplication/octet-stream; name=fix_typo_in_xlogutils_c.patchDownload
diff --git a/src/backend/access/transam/xlogutils.c b/src/backend/access/transam/xlogutils.c
index 28c07d3..fb7f2e7 100644
--- a/src/backend/access/transam/xlogutils.c
+++ b/src/backend/access/transam/xlogutils.c
@@ -780,7 +780,7 @@ XLogRead(char *buf, TimeLineID tli, XLogRecPtr startptr, Size count)
  *
  * We can't just check the timeline when we read a page on a different segment
  * to the last page. We could've received a timeline switch from a cascading
- * upstream, so the current segment ends apruptly (possibly getting renamed to
+ * upstream, so the current segment ends abruptly (possibly getting renamed to
  * .partial) and we have to switch to a new one.  Even in the middle of reading
  * a page we could have to dump the cached page and switch to a new TLI.
  *
#2Peter Eisentraut
peter.eisentraut@2ndquadrant.com
In reply to: Masahiko Sawada (#1)
Re: Comment typo in xlogutils.c

On 4/15/17 11:26, Masahiko Sawada wrote:

Attached patch for $subject.

s/apruptly/abruptly

Fixed, thanks.

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers