Fix typos and grammar in code and test comments
This fixes the grammar of some comments in a couple of tests (SQL and TAP), and in some C files. Author: Justin Pryzby Discussion: https://postgr.es/m/20220511020334.GH19626@telsasoft.com
This commit is contained in:
parent
0d3431497d
commit
45edde037e
|
@ -2270,7 +2270,7 @@ SELECT COUNT(*) = 8::bigint AS t FROM try;
|
|||
|
||||
INSERT INTO try
|
||||
VALUES ( to_char( now()::timestamp, 'HH12:MI:SS') ),
|
||||
( to_char( now() + '1 sec'::interval, 'HH12:MI:SS') ), -- timetamptz
|
||||
( to_char( now() + '1 sec'::interval, 'HH12:MI:SS') ), -- timestamptz
|
||||
( to_char( '15h 2m 12s'::interval, 'HH24:MI:SS') ),
|
||||
( to_char( current_date, '999') ),
|
||||
( to_char( 125::int, '999') ),
|
||||
|
|
|
@ -2270,7 +2270,7 @@ SELECT COUNT(*) = 8::bigint AS t FROM try;
|
|||
|
||||
INSERT INTO try
|
||||
VALUES ( to_char( now()::timestamp, 'HH12:MI:SS') ),
|
||||
( to_char( now() + '1 sec'::interval, 'HH12:MI:SS') ), -- timetamptz
|
||||
( to_char( now() + '1 sec'::interval, 'HH12:MI:SS') ), -- timestamptz
|
||||
( to_char( '15h 2m 12s'::interval, 'HH24:MI:SS') ),
|
||||
( to_char( current_date, '999') ),
|
||||
( to_char( 125::int, '999') ),
|
||||
|
|
|
@ -696,7 +696,7 @@ SELECT to_timestamp('05 Dec 2000', 'DD Mon YYYY'::citext)
|
|||
SELECT COUNT(*) = 8::bigint AS t FROM try;
|
||||
INSERT INTO try
|
||||
VALUES ( to_char( now()::timestamp, 'HH12:MI:SS') ),
|
||||
( to_char( now() + '1 sec'::interval, 'HH12:MI:SS') ), -- timetamptz
|
||||
( to_char( now() + '1 sec'::interval, 'HH12:MI:SS') ), -- timestamptz
|
||||
( to_char( '15h 2m 12s'::interval, 'HH24:MI:SS') ),
|
||||
( to_char( current_date, '999') ),
|
||||
( to_char( 125::int, '999') ),
|
||||
|
|
|
@ -246,7 +246,7 @@ BuildTupleHashTableExt(PlanState *parent,
|
|||
}
|
||||
|
||||
/*
|
||||
* BuildTupleHashTable is a backwards-compatibilty wrapper for
|
||||
* BuildTupleHashTable is a backwards-compatibility wrapper for
|
||||
* BuildTupleHashTableExt(), that allocates the hashtable's metadata in
|
||||
* tablecxt. Note that hashtables created this way cannot be reset leak-free
|
||||
* with ResetTupleHashTable().
|
||||
|
|
|
@ -4536,7 +4536,7 @@ transformJsonParseExpr(ParseState *pstate, JsonParseExpr *jsexpr)
|
|||
else
|
||||
{
|
||||
/*
|
||||
* Coerce argument to target type using CAST for compatibilty with PG
|
||||
* Coerce argument to target type using CAST for compatibility with PG
|
||||
* function-like CASTs.
|
||||
*/
|
||||
arg = transformJsonValueExprExt(pstate, jsexpr->expr, JS_FORMAT_JSON,
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
/*-------------------------------------------------------------------------
|
||||
*
|
||||
* basebackup_target.c
|
||||
* Base backups can be "targetted," which means that they can be sent
|
||||
* Base backups can be "targeted", which means that they can be sent
|
||||
* somewhere other than to the client which requested the backup.
|
||||
* Furthermore, new targets can be defined by extensions. This file
|
||||
* contains code to support that functionality.
|
||||
|
|
|
@ -423,7 +423,7 @@ bbstreamer_tar_archiver_content(bbstreamer *streamer,
|
|||
data = buffer;
|
||||
len = pad_bytes;
|
||||
|
||||
/* Don't do this agian unless we replace another header. */
|
||||
/* Don't do this again unless we replace another header. */
|
||||
mystreamer->rearchive_member = false;
|
||||
}
|
||||
else if (context == BBSTREAMER_ARCHIVE_TRAILER)
|
||||
|
|
|
@ -141,7 +141,7 @@ move(
|
|||
# Restart the node.
|
||||
$node_c->start;
|
||||
|
||||
# set RewindTest::node_primary to point to the rewinded node, so that we can
|
||||
# set RewindTest::node_primary to point to the rewound node, so that we can
|
||||
# use check_query()
|
||||
$node_primary = $node_c;
|
||||
|
||||
|
|
|
@ -47,7 +47,7 @@ mkdir "$standby_pgdata/tst_both_dir";
|
|||
append_to_file "$standby_pgdata/tst_both_dir/file1", 'a';
|
||||
|
||||
# Run pg_rewind and pipe the output from the run into the extra file we want
|
||||
# to copy. This will ensure that the file is continously growing during the
|
||||
# to copy. This will ensure that the file is continuously growing during the
|
||||
# copy operation and the result will be an error.
|
||||
my $ret = run_log(
|
||||
[
|
||||
|
|
|
@ -5481,7 +5481,7 @@ INSERT INTO bla VALUES ('Susie'); -- succeeds
|
|||
INSERT INTO bla VALUES ('Rosalyn') \; -- will rollback
|
||||
SELECT 'before error' AS show \; -- will show nevertheless!
|
||||
SELECT psql_error('boum!') \; -- failure
|
||||
SELECT 'after error' AS noshow; -- hidden by preceeding error
|
||||
SELECT 'after error' AS noshow; -- hidden by preceding error
|
||||
show
|
||||
--------------
|
||||
before error
|
||||
|
|
|
@ -1432,7 +1432,7 @@ INSERT INTO bla VALUES ('Susie'); -- succeeds
|
|||
INSERT INTO bla VALUES ('Rosalyn') \; -- will rollback
|
||||
SELECT 'before error' AS show \; -- will show nevertheless!
|
||||
SELECT psql_error('boum!') \; -- failure
|
||||
SELECT 'after error' AS noshow; -- hidden by preceeding error
|
||||
SELECT 'after error' AS noshow; -- hidden by preceding error
|
||||
INSERT INTO bla(s) VALUES ('Moe') \; -- will rollback
|
||||
SELECT psql_error('bam!');
|
||||
INSERT INTO bla VALUES ('Miss Wormwood'); -- succeeds
|
||||
|
|
|
@ -135,7 +135,7 @@ sub get_sslkey
|
|||
=item $backend->set_server_cert(params)
|
||||
|
||||
Change the configuration to use given server cert, key and crl file(s). The
|
||||
following paramters are supported:
|
||||
following parameters are supported:
|
||||
|
||||
=over
|
||||
|
||||
|
|
Loading…
Reference in a new issue