Remove some unused index directives.

This commit is contained in:
Dave Page 2017-10-11 11:57:59 +01:00
parent 04beec1309
commit 1f4a814e72
5 changed files with 113 additions and 113 deletions

View File

@ -1,8 +1,8 @@
.. _connect_error: .. _connect_error:
************************** ******************
`Connection error`:index: `Connection error`
************************** ******************
When connecting to a PostgreSQL server, you may get an error message. If you encounter an error message, please review the message carefully; each error message attempts to incorporate the information you'll need to resolve the problem. For more details about specific errors, please locate the error message in the list below: When connecting to a PostgreSQL server, you may get an error message. If you encounter an error message, please review the message carefully; each error message attempts to incorporate the information you'll need to resolve the problem. For more details about specific errors, please locate the error message in the list below:

View File

@ -1,8 +1,8 @@
.. _debugger: .. _debugger:
************************* ******************
`pgAdmin Debugger`:index: `pgAdmin Debugger`
************************* ******************
.. image:: images/debug_main.png .. image:: images/debug_main.png

View File

@ -1,9 +1,9 @@
.. _pgagent_install: .. _pgagent_install:
*************************** ********************
`Installing pgAgent`:index: `Installing pgAgent`
*************************** ********************
pgAgent runs as a daemon on Unix systems, and a service on Windows systems. In most cases it will run on the database server itself - for this reason, pgAgent is not automatically configured when pgAdmin is installed. In some cases however, it may be preferable to run pgAgent on multiple systems, against the same database; individual jobs may be targeted at a particular host, or left for execution by any host. Locking prevents execution of the same instance of a job by multiple hosts. pgAgent runs as a daemon on Unix systems, and a service on Windows systems. In most cases it will run on the database server itself - for this reason, pgAgent is not automatically configured when pgAdmin is installed. In some cases however, it may be preferable to run pgAgent on multiple systems, against the same database; individual jobs may be targeted at a particular host, or left for execution by any host. Locking prevents execution of the same instance of a job by multiple hosts.

View File

@ -1,9 +1,9 @@
.. _pgagent_jobs: .. _pgagent_jobs:
******************************* ************************
`Creating a pgAgent Job`:index: `Creating a pgAgent Job`
******************************* ************************
pgAgent is a scheduling agent that runs and manages jobs; each job consists of steps and schedules. pgAgent is a scheduling agent that runs and manages jobs; each job consists of steps and schedules.

View File

@ -1,9 +1,9 @@
.. _using_pgagent: .. _using_pgagent:
********************** ***************
`Using pgAgent`:index: `Using pgAgent`
********************** ***************
pgAgent is a scheduling agent that runs and manages jobs; each job consists of one or more steps and schedules. If two or more jobs are scheduled to execute concurrently, pgAgent will execute the jobs in parallel (each with it's own thread). pgAgent is a scheduling agent that runs and manages jobs; each job consists of one or more steps and schedules. If two or more jobs are scheduled to execute concurrently, pgAgent will execute the jobs in parallel (each with it's own thread).