database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-27 12:41:57 +03:00
Code Activity

Remove uses of "slave" in replication contexts

Browse Source 
This affects mostly code comments, some documentation, and tests.
Official APIs already used "standby".
This commit is contained in:
Peter Eisentraut
2017-08-07 17:42:47 -04:00
parent d6391b03b3
commit a1ef920e27
21 changed files with 103 additions and 103 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
contrib/dblink/sql/dblink.sql
View File

@ -160,14 +160,14 @@ SELECT *
FROM dblink('SELECT * FROM foo') AS t(a int, b text, c text[])
WHERE t.a > 7;
-- 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);
-- create a persistent connection
SELECT dblink_connect(connection_parameters());
-- 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);
@ -316,7 +316,7 @@ WHERE t.a > 7;
-- create a named persistent connection
SELECT dblink_connect('myconn',connection_parameters());
-- 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);