Skip to content

Commit 8b5a399

Browse files
peterepetere
committed
Remove whitespace from end of lines
1 parent d7eb6f4 commit 8b5a399

File tree

12 files changed

+33
-33
lines changed

12 files changed

+33
-33
lines changed

‎doc/src/sgml/maintenance.sgml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -632,7 +632,7 @@ HINT: Stop the postmaster and use a standalone backend to VACUUM in "mydb".
632632
<varname>autovacuum_max_workers</> databases to be processed,
633633
the next database will be processed as soon as the first worker finishes.
634634
Each worker process will check each table within its database and
635-
execute <command>VACUUM</> and/or <command>ANALYZE</> as needed.
635+
execute <command>VACUUM</> and/or <command>ANALYZE</> as needed.
636636
<varname>log_autovacuum_min_duration</varname> can be used to monitor
637637
autovacuum activity.
638638
</para>

‎doc/src/sgml/ref/create_table.sgml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -336,7 +336,7 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI
336336
<para>
337337
Not-null constraints are always copied to the new table.
338338
<literal>CHECK</literal> constraints will be copied only if
339-
<literal>INCLUDING CONSTRAINTS</literal> is specified.
339+
<literal>INCLUDING CONSTRAINTS</literal> is specified.
340340
Indexes, <literal>PRIMARY KEY</>, and <literal>UNIQUE</> constraints
341341
on the original table will be created on the new table only if the
342342
<literal>INCLUDING INDEXES</literal> clause is specified.

‎doc/src/sgml/ref/notify.sgml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ NOTIFY <replaceable class="PARAMETER">channel</replaceable> [ , <replaceable cla
3333
with an optional <quote>payload</> string to each client application that
3434
has previously executed
3535
<command>LISTEN <replaceable class="parameter">channel</></command>
36-
for the specified channel name in the current database.
36+
for the specified channel name in the current database.
3737
Notifications are visible to all users.
3838
</para>
3939

‎doc/src/sgml/ref/pg_dump.sgml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -324,7 +324,7 @@ PostgreSQL documentation
324324
For a consistent backup, the database server needs to support synchronized snapshots,
325325
a feature that was introduced in <productname>PostgreSQL</productname> 9.2. With this
326326
feature, database clients can ensure they see the same data set even though they use
327-
different connections. <command>pg_dump -j</command> uses multiple database
327+
different connections. <command>pg_dump -j</command> uses multiple database
328328
connections; it connects to the database once with the master process and
329329
once again for each worker job. Without the synchronized snapshot feature, the
330330
different worker jobs wouldn't be guaranteed to see the same data in each connection,

‎src/Makefile.global.in

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -434,7 +434,7 @@ PL_TESTDB = pl_regression
434434
CONTRIB_TESTDB = contrib_regression
435435
ifneq ($(MODULE_big),)
436436
CONTRIB_TESTDB_MODULE = contrib_regression_$(MODULE_big)
437-
else
437+
else
438438
ifneq ($(MODULES),)
439439
CONTRIB_TESTDB_MODULE = contrib_regression_$(MODULES)
440440
else

‎src/backend/catalog/system_views.sql

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -788,10 +788,10 @@ CREATE OR REPLACE FUNCTION
788788
pg_start_backup(label text, fast boolean DEFAULT false)
789789
RETURNS text STRICT VOLATILE LANGUAGE internal AS 'pg_start_backup';
790790

791-
CREATE OR REPLACE FUNCTION
791+
CREATE OR REPLACE FUNCTION
792792
json_populate_record(base anyelement, from_json json, use_json_as_text boolean DEFAULT false)
793793
RETURNS anyelement LANGUAGE internal STABLE AS 'json_populate_record';
794794

795-
CREATE OR REPLACE FUNCTION
795+
CREATE OR REPLACE FUNCTION
796796
json_populate_recordset(base anyelement, from_json json, use_json_as_text boolean DEFAULT false)
797797
RETURNS SETOF anyelement LANGUAGE internal STABLE ROWS 100 AS 'json_populate_recordset';

‎src/test/regress/expected/json.out

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -466,15 +466,15 @@ INSERT INTO test_json VALUES
466466
('scalar','"a scalar"'),
467467
('array','["zero", "one","two",null,"four","five"]'),
468468
('object','{"field1":"val1","field2":"val2","field3":null}');
469-
SELECT test_json -> 'x'
469+
SELECT test_json -> 'x'
470470
FROM test_json
471471
WHERE json_type = 'scalar';
472472
ERROR: cannot extract element from a scalar
473-
SELECT test_json -> 'x'
473+
SELECT test_json -> 'x'
474474
FROM test_json
475475
WHERE json_type = 'array';
476476
ERROR: cannot extract field from a non-object
477-
SELECT test_json -> 'x'
477+
SELECT test_json -> 'x'
478478
FROM test_json
479479
WHERE json_type = 'object';
480480
?column?
@@ -490,19 +490,19 @@ WHERE json_type = 'object';
490490
"val2"
491491
(1 row)
492492

493-
SELECT test_json->>'field2'
493+
SELECT test_json->>'field2'
494494
FROM test_json
495495
WHERE json_type = 'object';
496496
?column?
497497
----------
498498
val2
499499
(1 row)
500500

501-
SELECT test_json -> 2
501+
SELECT test_json -> 2
502502
FROM test_json
503503
WHERE json_type = 'scalar';
504504
ERROR: cannot extract element from a scalar
505-
SELECT test_json -> 2
505+
SELECT test_json -> 2
506506
FROM test_json
507507
WHERE json_type = 'array';
508508
?column?

‎src/test/regress/sql/json.sql

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -139,31 +139,31 @@ INSERT INTO test_json VALUES
139139
('array','["zero", "one","two",null,"four","five"]'),
140140
('object','{"field1":"val1","field2":"val2","field3":null}');
141141

142-
SELECT test_json -> 'x'
142+
SELECT test_json -> 'x'
143143
FROM test_json
144144
WHERE json_type = 'scalar';
145145

146-
SELECT test_json -> 'x'
146+
SELECT test_json -> 'x'
147147
FROM test_json
148148
WHERE json_type = 'array';
149149

150-
SELECT test_json -> 'x'
150+
SELECT test_json -> 'x'
151151
FROM test_json
152152
WHERE json_type = 'object';
153153

154154
SELECT test_json->'field2'
155155
FROM test_json
156156
WHERE json_type = 'object';
157157

158-
SELECT test_json->>'field2'
158+
SELECT test_json->>'field2'
159159
FROM test_json
160160
WHERE json_type = 'object';
161161

162-
SELECT test_json -> 2
162+
SELECT test_json -> 2
163163
FROM test_json
164164
WHERE json_type = 'scalar';
165165

166-
SELECT test_json -> 2
166+
SELECT test_json -> 2
167167
FROM test_json
168168
WHERE json_type = 'array';
169169

‎src/tools/msvc/Mkvcbuild.pm

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -523,8 +523,8 @@ sub mkvcbuild
523523
my $mf = Project::read_file(
524524
'src\backend\utils\mb\conversion_procs\\' . $sub . '\Makefile');
525525
my $p = $solution->AddProject($sub, 'dll', 'conversion procs');
526-
$p->AddFile('src\backend\utils\mb\conversion_procs\\'
527-
. $sub . '\\'
526+
$p->AddFile('src\backend\utils\mb\conversion_procs\\'
527+
. $sub . '\\'
528528
. $sub
529529
. '.c');
530530
if ($mf =~ m{^SRCS\s*\+=\s*(.*)$}m)

‎src/tools/pgindent/perltidyrc

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,12 @@
1-
--add-whitespace
2-
--backup-and-modify-in-place
1+
--add-whitespace
2+
--backup-and-modify-in-place
33
--delete-old-whitespace
4-
--entab-leading-whitespace=4
5-
--keep-old-blank-lines=2
4+
--entab-leading-whitespace=4
5+
--keep-old-blank-lines=2
66
--maximum-line-length=78
7-
--nospace-for-semicolon
7+
--nospace-for-semicolon
88
--opening-brace-on-new-line
99
--output-line-ending=unix
10-
--paren-tightness=2
11-
--vertical-tightness=2
10+
--paren-tightness=2
11+
--vertical-tightness=2
1212
--vertical-tightness-closing=2

0 commit comments

Comments
 (0)