* with the answer changing under them, or that they already hold some
* appropriate lock, and therefore return the first answer we get without
* checking for invalidation messages. Also, if the requested lock is
- * already held, no LockRelationOid will not AcceptInvalidationMessages,
+ * already held, LockRelationOid will not AcceptInvalidationMessages,
* so we may fail to notice a change. We could protect against that case
* by calling AcceptInvalidationMessages() before beginning this loop, but
* that would add a significant amount overhead, so for now we don't.
* the same name which already exists in that namespace, or to InvalidOid if
* no such relation exists.
*
- * If lockmode != NoLock, the specified lock mode is acquire on the existing
+ * If lockmode != NoLock, the specified lock mode is acquired on the existing
* relation, if any, provided that the current user owns the target relation.
* However, if lockmode != NoLock and the user does not own the target
* relation, we throw an ERROR, as we must not try to lock relations the
* Just a workaround of unknown locking problem with writing in UDP socket
* under high load: Client's pgsql backend sleeps infinitely in
* WaitForMultipleObjectsEx, pgstat process sleeps in pgwin32_select().
- * So, we will wait with small timeout(0.1 sec) and if sockect is still
+ * So, we will wait with small timeout(0.1 sec) and if socket is still
* blocked, try WSASend (see comments in pgwin32_select) and wait again.
*/
if ((what & FD_WRITE) && isUDP)
/* Make sure we are in proper schema */
selectSourceSchema(fout, collinfo->dobj.namespace->dobj.name);
- /* Get conversion-specific details */
+ /* Get collation-specific details */
appendPQExpBuffer(query, "SELECT "
"collcollate, "
"collctype "