Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
postgresql-common
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container registry
Model registry
Operate
Environments
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
PostgreSQL
postgresql-common
Commits
194133f1
Commit
194133f1
authored
19 years ago
by
Martin Pitt
Browse files
Options
Downloads
Patches
Plain Diff
* pg_wrapper: Improve manpage POD, describe the precise rules for cluster
selection.
parent
9ed762e7
No related branches found
No related tags found
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
postgresql-common/debian/changelog
+3
-2
3 additions, 2 deletions
postgresql-common/debian/changelog
postgresql-common/pg_wrapper
+47
-6
47 additions, 6 deletions
postgresql-common/pg_wrapper
with
50 additions
and
8 deletions
postgresql-common/debian/changelog
+
3
−
2
View file @
194133f1
postgresql-common (58) unstable; urgency=low
postgresql-common (58) unstable; urgency=low
*
* pg_wrapper: Improve manpage POD, describe the precise rules for cluster
selection.
-- Martin Pitt <mpitt@debian.org>
Fri, 30
Ju
n
2006
00:22:34
+0200
-- Martin Pitt <mpitt@debian.org>
Sat, 22
Ju
l
2006
17:45:56
+0200
postgresql-common (57) unstable; urgency=low
postgresql-common (57) unstable; urgency=low
...
...
This diff is collapsed.
Click to expand it.
postgresql-common/pg_wrapper
+
47
−
6
View file @
194133f1
...
@@ -89,12 +89,53 @@ configured cluster and database for the user and calls the appropriate version
...
@@ -89,12 +89,53 @@ configured cluster and database for the user and calls the appropriate version
of the desired program to connect to that cluster and database, supplying any
of the desired program to connect to that cluster and database, supplying any
specifed options to that command.
specifed options to that command.
By default, the cluster is determined from the configuration files
The target cluster is selected by the following means, in descending order of
L<user_clusters(5)> and L<postgresqlrc(5)>. However, this can be overriden by
precedence:
specifying the C<$PGCLUSTER> environment variable or the B<--cluster>
I<version>/I<cluster> option. I<cluster> is either the name of a local
=over
cluster, or takes the form I<host>:I<port> for a remote cluster. If I<port> is
left empty (i. e. you just specify I<host:>), it defaults to 5432.
=item 1.
explicit specification with the B<--cluster> option
=item 2.
explicit specification with the B<PGCLUSTER> environment variable
=item 3.
matching entry in C<~/.postgresqlrc> (see L<postgresqlrc(5)>), if that
file exists
=item 4.
matching entry in C</etc/postgresql-common/user_clusters> (see
L<user_clusters(5)>), if that file exists
=item 5.
If only one local cluster exists, that one will be selected.
=item 6.
If several local clusters exist, the one listening on the default port 5432
will be selected.
=back
If none of these rules match, B<pg_wrapper> aborts with an error.
=head1 OPTIONS
=over
=item B<--cluster> I<version>B</>I<cluster>
I<cluster> is either the name of a local cluster, or takes the form
I<host>:I<port> for a remote cluster. If I<port> is left empty (i. e. you just
specify I<host:>), it defaults to 5432.
=back
=head1 ENVIRONMENT
=head1 ENVIRONMENT
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment