Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 98105e5

Browse files
committed
1 parent 58651d8 commit 98105e5

File tree

3 files changed

+3
-3
lines changed

3 files changed

+3
-3
lines changed

src/backend/storage/lmgr/README

+1-1
Original file line numberDiff line numberDiff line change
@@ -692,7 +692,7 @@ User Locks (Advisory Locks)
692692
User locks are handled totally on the application side as long term
693693
cooperative locks which may extend beyond the normal transaction boundaries.
694694
Their purpose is to indicate to an application that someone is `working'
695-
on an item. So it is possible to put an user lock on a tuple's oid,
695+
on an item. So it is possible to put a user lock on a tuple's oid,
696696
retrieve the tuple, work on it for an hour and then update it and remove
697697
the lock. While the lock is active other clients can still read and write
698698
the tuple but they can be aware that it has been locked at the application

src/backend/utils/adt/pg_locale.c

+1-1
Original file line numberDiff line numberDiff line change
@@ -1068,7 +1068,7 @@ get_iso_localename(const char *winlocname)
10681068
LOCALE_NAME_MAX_LENGTH);
10691069

10701070
/*
1071-
* If the lc_messages is already an Unix-style string, we have a direct
1071+
* If the lc_messages is already a Unix-style string, we have a direct
10721072
* match with LOCALE_SNAME, e.g. en-US, en_US.
10731073
*/
10741074
ret_val = GetLocaleInfoEx(wc_locale_name, LOCALE_SNAME, (LPWSTR) &buffer,

src/include/access/attnum.h

+1-1
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ typedef int16 AttrNumber;
3636

3737
/*
3838
* AttrNumberIsForUserDefinedAttr
39-
* True iff the attribute number corresponds to an user defined attribute.
39+
* True iff the attribute number corresponds to a user defined attribute.
4040
*/
4141
#define AttrNumberIsForUserDefinedAttr(attributeNumber) \
4242
((bool) ((attributeNumber) > 0))

0 commit comments

Comments
 (0)