Re: Comment typo in slot.c

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Cc: PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Comment typo in slot.c
Date: 2016-02-05 13:11:34
Message-ID: CA+Tgmob3Dkj_5eVVe_LdHBuKRT-P_OXH7qN55ppkUc+Obsna+g@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Feb 4, 2016 at 4:39 AM, Michael Paquier
<michael(dot)paquier(at)gmail(dot)com> wrote:
> I just bumped into the following typo in slot.c:
> /*
> * If we'd now fail - really unlikely - we wouldn't know
> whether this slot
> * would persist after an OS crash or not - so, force a restart. The
> - * restart would try to fysnc this again till it works.
> + * restart would try to fsync this again till it works.
> */
> START_CRIT_SECTION();

Committed.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Ashutosh Bapat 2016-02-05 14:09:55 Re: postgres_fdw join pushdown (was Re: Custom/Foreign-Join-APIs)
Previous Message Robert Haas 2016-02-05 13:06:13 Re: Generalizing SortSupport for text to work with char(n), bytea, and alternative opclasses