24
24
notation), or the path to a Compiled HTML Help (.chm) file (on
25
25
Windows), an HTML Help project (.hhp) file, or a Zip archive containing the HTML
26
26
files and the HTML Help project file. The PostgreSQL Help is used when selected
27
from the Help menu, or when working with many database objects on PostgreSQL.
27
from the Help menu, or when working with many database objects on PostgreSQL
28
28
servers.<br> </li>
30
30
<li><b>EDB help path</b> - This option is used to specify the path
32
32
help path. The EnterpriseDB Help is used when selected from the Help menu,
33
33
or when working with many database objects on EnterpriseDB servers.<br> </li>
35
<li><b>GP help path</b> - This option is used to specify the path
36
to the Greenplum help files, and may be configured in the same way as the PG
37
help path. The Greenplum Help is used when selected from the Help menu,
38
or when working with many database objects on Greenplum servers.<br> </li>
35
40
<li><b>Slony help path</b> - This option is used to specify the path
36
41
to the Slony help files, and may be configured in the same way as the PG
37
42
help path. The Slony Help is used when selected from the Help menu.<br> </li>
39
<li><b>System schemas</b>- You can suppress the display of additional schemas,
40
by declaring them a system schema. This field takes a list of comma separated strings.<br> </li>
44
<li><b>System schemas</b> - You can suppress the display of additional schemas,
45
by declaring them a system schema. This field takes a list of comma separated strings.<br> </li>
42
<li><b>Slony-I path</b>- To enable pgAdmin III to create Slony-I replication clusters
47
<li><b>Slony-I path</b> - To enable pgAdmin III to create Slony-I replication clusters
43
48
from scratch, you need to enter the path to the Slony-I script installation directory here. If no
44
49
valid scripts can be found, only joining existing clusters is possible.
47
<li><b>PG bin path</b>- This should be set to the path to the standard PostgreSQL pg_dump, pg_restore
52
<li><b>PG bin path</b> - This should be set to the path to the standard PostgreSQL pg_dump, pg_restore
48
53
and pg_dumpall utilities. pgAdmin will use these for backing up and restoring your PostgreSQL databases.
49
If this path is not set, pgAdmin will attempt to find the utilities in it's installation directory,
54
If this path is not set, pgAdmin will attempt to find the utilities in its installation directory,
50
55
the 'hint' directory set by a local PostgreSQL installation (on Windows) and in the system path.
53
<li><b>EDB bin path</b>- This should be set to the path to the EnterpriseDB pg_dump, pg_restore
58
<li><b>EDB bin path</b> - This should be set to the path to the EnterpriseDB pg_dump, pg_restore
54
59
and pg_dumpall utilities. pgAdmin will use these for backing up and restoring your EnterpriseDB databases.
55
60
If this path is not set, pgAdmin will attempt to find the utilities in standard locations used by
64
<li><b>GP bin path</b> - This should be set to the path to the Greenplum pg_dump, pg_restore
65
and pg_dumpall utilities. pgAdmin will use these for backing up and restoring your Greenplum databases.
66
If this path is not set, pgAdmin will attempt to find the utilities in standard locations used by
70
<li><b>Ignore server/utility version mismatches</b> - When checked, pgAdmin will pass the '-i' option
71
to utilities such as <i>pg_dump</i> which will allow utilities from one version of the database to
72
be used with another version. This option should be use with extreme care as it may cause errors to
73
occur during backup or restore options.