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
0688e720
Commit
0688e720
authored
20 years ago
by
Martin Pitt
Browse files
Options
Downloads
Patches
Plain Diff
pod'ify pg_wrapper manpage
parent
97cf0f96
No related branches found
No related tags found
No related merge requests found
Changes
3
Hide whitespace changes
Inline
Side-by-side
Showing
3 changed files
postgresql-common-1/debian/rules
+1
-1
1 addition, 1 deletion
postgresql-common-1/debian/rules
postgresql-common-1/pg_wrapper
+36
-0
36 additions, 0 deletions
postgresql-common-1/pg_wrapper
postgresql-common-1/pg_wrapper.1
+0
-36
0 additions, 36 deletions
postgresql-common-1/pg_wrapper.1
with
37 additions
and
37 deletions
postgresql-common-1/debian/rules
+
1
−
1
View file @
0688e720
...
...
@@ -2,7 +2,7 @@
include /usr/share/cdbs/1/rules/debhelper.mk
POD2MAN=pod2man --center "Debian PostgreSQL infrastructure" -r "Debian"
PODPROGS=pg_ctlcluster
PODPROGS=pg_ctlcluster
pg_wrapper
build/postgresql-common::
for p in $(PODPROGS); do $(POD2MAN) $$p > $$p.1; done
...
...
This diff is collapsed.
Click to expand it.
postgresql-common-1/pg_wrapper
+
36
−
0
View file @
0688e720
...
...
@@ -32,3 +32,39 @@ $ENV{'PGDATABASE'} = $db if $db;
push
@args
,
@ARGV
;
exec
@args
;
__END__
=head1 NAME
pg_wrapper - wrapper for PostgreSQL client commands
=head1 DESCRIPTION
This program is run only as a link to names which correspond to PostgreSQL
programs in B</usr/lib/postgresql/>I<version>B</bin>. It finds the correct
cluster and database for the user and calls the correct version of the desired
program to connect to that cluster and database, supplying any specifed options
to that command.
=head1 FILES
=over
=item B</etc/postgresql-common/user_clusters>
stores the default cluster and database for users and groups as set by
the administrators.
=item B<$HOME/.postgresqlrc>
stores defaults set by the user himself.
=back
=head1 SEE ALSO
L<pg_default(1)>, L<pg_exec(1)>
=head1 AUTHOR
Martin Pitt L<E<lt>mpitt@debian.orgE<gt>>
This diff is collapsed.
Click to expand it.
postgresql-common-1/pg_wrapper.1
deleted
100644 → 0
+
0
−
36
View file @
97cf0f96
.\" Hey, Emacs! This is an -*- nroff -*- source file.
.\"
.TH PG_WRAPPER 1 "October 2003" "Debian Project" "Debian Linux"
.SH NAME
pg_wrapper \- Wrapper program for PostgreSQL commands
.SH DESCRIPTION
.P
This program is run only as a link to names
which correspond to PostgreSQL programs in
.RI /usr/lib/postgresql/ version /bin.
If the specified host is the local machine, it finds the correct
cluster and database for the user and calls
the correct version of the desired program to connect to that cluster and
database, supplying any specifed options to that command.
.P
If a remote host is specified,
.B pg_wrapper
behaves like
.B pg_exec.
.SH FILES
.TP
.I /etc/postgresql-common/user_clusters
stores the default cluster and database for users and groups as set by
the administrators. By setting the FORCED flag for a user or group, it
is possible for an administrator to override a
user's choices so that the user can connect only to the cluster and
database selected for him.
.TP
.I $HOME/.postgresqlrc
stores defaults set by the user himself.
.SH SEE ALSO
.BR pg_default (1),
.BR pg_exec (1)
.SH AUTHOR
Oliver Elphick <olly@lfix.co.uk>
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