diff options
| author | Peter Eisentraut <peter_e@gmx.net> | 2017-08-07 17:42:47 -0400 |
|---|---|---|
| committer | Peter Eisentraut <peter_e@gmx.net> | 2017-08-10 22:55:41 -0400 |
| commit | a1ef920e27ba6ab3602aaf6d6751d8628fac1af8 (patch) | |
| tree | 51485b2898ae4b01b2e71ad5e40a7d3b02d75f91 /contrib/dblink/expected | |
| parent | d6391b03b3025372620925e5746e65c288a1e371 (diff) | |
| download | postgresql-a1ef920e27ba6ab3602aaf6d6751d8628fac1af8.tar.gz | |
Remove uses of "slave" in replication contexts
This affects mostly code comments, some documentation, and tests.
Official APIs already used "standby".
Diffstat (limited to 'contrib/dblink/expected')
| -rw-r--r-- | contrib/dblink/expected/dblink.out | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/contrib/dblink/expected/dblink.out b/contrib/dblink/expected/dblink.out index 4b6d26e574..511691e57f 100644 --- a/contrib/dblink/expected/dblink.out +++ b/contrib/dblink/expected/dblink.out @@ -270,7 +270,7 @@ SELECT * FROM dblink('SELECT * FROM foo') AS t(a int, b text, c text[]) WHERE t.a > 7; ERROR: connection not available --- put more data into our slave table, first using arbitrary connection syntax +-- put more data into our table, first using arbitrary connection syntax -- but truncate the actual return value so we can use diff to check for success SELECT substr(dblink_exec(connection_parameters(),'INSERT INTO foo VALUES(10,''k'',''{"a10","b10","c10"}'')'),1,6); substr @@ -285,7 +285,7 @@ SELECT dblink_connect(connection_parameters()); OK (1 row) --- put more data into our slave table, using persistent connection syntax +-- put more data into our table, using persistent connection syntax -- but truncate the actual return value so we can use diff to check for success SELECT substr(dblink_exec('INSERT INTO foo VALUES(11,''l'',''{"a11","b11","c11"}'')'),1,6); substr @@ -610,7 +610,7 @@ SELECT dblink_connect('myconn',connection_parameters()); OK (1 row) --- put more data into our slave table, using named persistent connection syntax +-- put more data into our table, using named persistent connection syntax -- but truncate the actual return value so we can use diff to check for success SELECT substr(dblink_exec('myconn','INSERT INTO foo VALUES(11,''l'',''{"a11","b11","c11"}'')'),1,6); substr |