python-postgres
diff --git a/‎postgresql/documentation/bin.txt‎
Lines changed: 13 additions & 13 deletions b/‎postgresql/documentation/bin.txt‎
Lines changed: 13 additions & 13 deletions
@@ -4,8 +4,8 @@ Commands
 This chapter discusses the usage of the available console scripts.
 
 
-``pg_python``
-=============
+postgresql.bin.pg_python
+========================
 
 The ``pg_python`` command provides a simple way to write Python scripts against a
 single target database. It acts like the regular Python console command, but
@@ -37,7 +37,7 @@ with the following built-ins:
 pg_python Usage
 ---------------
 
-Usage: pg_python.py [connection options] [script] ...
+Usage: postgresql.bin.pg_python [connection options] [script] ...
 
 Options:
   --unix=UNIX           path to filesystem socket
@@ -85,17 +85,17 @@ pg_python Examples
 
 Module execution taking advantage of the new built-ins::
 
-	$ pg_python -h localhost -W -m timeit "prepare('SELECT 1').first()"
+	$ python3 -m postgresql.bin.pg_python -h localhost -W -m timeit "prepare('SELECT 1').first()"
 	Password for pg_python[pq://jwp@localhost:5432]:
 	1000 loops, best of 3: 1.35 msec per loop
 
-	$ pg_python -h localhost -W -m timeit -s "ps=prepare('SELECT 1')" "ps.first()"
+	$ python3 -m postgresql.bin.pg_python -h localhost -W -m timeit -s "ps=prepare('SELECT 1')" "ps.first()"
 	Password for pg_python[pq://jwp@localhost:5432]:
 	1000 loops, best of 3: 442 usec per loop
 
 Simple interactive usage::
 
-	$ pg_python -h localhost -W
+	$ python3 -m postgresql.bin.pg_python -h localhost -W
 	Password for pg_python[pq://jwp@localhost:5432]:
 	>>> ps = prepare('select 1')
 	>>> ps.first()
@@ -108,8 +108,8 @@ Simple interactive usage::
 	>>> sys.exit(0)
 
 
-``pg_dotconf``
-==============
+postgresql.bin.pg_dotconf
+=========================
 
 pg_dotconf is used to modify a PostgreSQL cluster's configuration file.
 It provides a means to apply settings specified from the command line and from a
@@ -124,7 +124,7 @@ file referenced using the ``-f`` option.
 pg_dotconf Usage
 ----------------
 
-Usage: pg_dotconf.py [--stdout] [-f filepath] postgresql.conf ([param=val]|[param])*
+Usage: postgresql.bin.pg_dotconf [--stdout] [-f filepath] postgresql.conf ([param=val]|[param])*
 
 Options:
   --version             show program's version number and exit
@@ -144,19 +144,19 @@ Modifying a simple configuration file::
 	$ echo "setting = value" >pg.conf
 
 	# change 'setting'
-	$ pg_dotconf pg.conf setting=newvalue
+	$ python3 -m postgresql.bin.pg_dotconf pg.conf setting=newvalue
 
 	$ cat pg.conf
 	setting = 'newvalue'
 
 	# new settings are appended to the file
-	$ pg_dotconf pg.conf another_setting=value
+	$ python3 -m postgresql.bin.pg_dotconf pg.conf another_setting=value
 	$ cat pg.conf
 	setting = 'newvalue'
 	another_setting = 'value'
 
 	# comment a setting
-	$ pg_dotconf pg.conf another_setting
+	$ python3 -m postgresql.bin.pg_dotconf pg.conf another_setting
 
 	$ cat pg.conf
 	setting = 'newvalue'
@@ -165,6 +165,6 @@ Modifying a simple configuration file::
 When a setting is given on the command line, it must been seen as one argument
 to the command, so it's *very* important to avoid invocations like::
 
-	$ pg_dotconf pg.conf setting = value
+	$ python3 -m postgresql.bin.pg_dotconf pg.conf setting = value
 	ERROR: invalid setting, '=' after 'setting'
 	HINT: Settings must take the form 'setting=value' or 'setting_name_to_comment'. Settings must also be received as a single argument.