3 PostgreSQL documentation
6 <refentry id=
"APP-DROPLANG">
8 <refentrytitle id=
"APP-DROPLANG-TITLE"><application>droplang
</application></refentrytitle>
9 <manvolnum>1</manvolnum>
10 <refmiscinfo>Application
</refmiscinfo>
14 <refname>droplang
</refname>
15 <refpurpose>remove a
<productname>PostgreSQL
</productname> procedural language
</refpurpose>
18 <indexterm zone=
"app-droplang">
19 <primary>droplang
</primary>
24 <command>droplang
</command>
25 <arg rep=
"repeat"><replaceable>connection-option
</replaceable></arg>
26 <arg choice=
"plain"><replaceable>langname
</replaceable></arg>
27 <arg><replaceable>dbname
</replaceable></arg>
29 <command>droplang
</command>
30 <arg rep=
"repeat"><replaceable>connection-option
</replaceable></arg>
31 <group choice=
"plain"><arg>--list
</arg><arg>-l
</arg></group>
32 <arg choice=
"plain"><replaceable>dbname
</replaceable></arg>
36 <refsect1 id=
"R1-APP-DROPLANG-1">
42 <application>droplang
</application> is a utility for removing an
43 existing programming language from a
44 <productname>PostgreSQL
</productname> database.
45 <application>droplang
</application> can drop any procedural language,
46 even those not supplied by the
<productname>PostgreSQL<
/> distribution.
49 Although backend programming languages can be removed directly using
50 several
<acronym>SQL
</acronym> commands, it is recommended to use
51 <application>droplang
</application> because it performs a number
52 of checks and is much easier to use. See
53 <xref linkend=
"sql-droplanguage" endterm=
"sql-droplanguage-title">
60 <title>Options
</title>
63 <application>droplang
</application> accepts the following command line arguments:
67 <term><replaceable class=
"parameter">langname
</replaceable></term>
70 Specifies the name of the backend programming language to be removed.
76 <term><option><optional>-d<
/> <replaceable class=
"parameter">dbname
</replaceable><
/></term>
77 <term><option><optional>--dbname<
/> <replaceable class=
"parameter">dbname
</replaceable><
/></term>
80 Specifies from which database the language should be removed.
81 The default is to use the database with the same name as the
88 <term><option>-e<
/></term>
89 <term><option>--echo<
/></term>
92 Display SQL commands as they are executed.
98 <term><option>-l<
/></term>
99 <term><option>--list<
/></term>
102 Show a list of already installed languages in the target database.
111 <application>droplang
</application> also accepts
112 the following command line arguments for connection parameters:
116 <term><option>-h
<replaceable class=
"parameter">host
</replaceable><
/></term>
117 <term><option>--host
<replaceable class=
"parameter">host
</replaceable><
/></term>
120 Specifies the host name of the machine on which the
122 is running. If host begins with a slash, it is used
123 as the directory for the Unix domain socket.
129 <term><option>-p
<replaceable class=
"parameter">port
</replaceable><
/></term>
130 <term><option>--port
<replaceable class=
"parameter">port
</replaceable><
/></term>
133 Specifies the Internet TCP/IP port or local Unix domain socket file
134 extension on which the server
135 is listening for connections.
141 <term><option>-U
<replaceable class=
"parameter">username
</replaceable><
/></term>
142 <term><option>--username
<replaceable class=
"parameter">username
</replaceable><
/></term>
145 User name to connect as.
151 <term><option>-w<
/></term>
152 <term><option>--no-password<
/></term>
155 Never issue a password prompt. If the server requires
156 password authentication and a password is not available by
157 other means such as a
<filename>.pgpass
</filename> file, the
158 connection attempt will fail. This option can be useful in
159 batch jobs and scripts where no user is present to enter a
166 <term><option>-W<
/></term>
167 <term><option>--password<
/></term>
170 Force
<application>droplang
</application> to prompt for a
171 password before connecting to a database.
175 This option is never essential, since
176 <application>droplang
</application> will automatically prompt
177 for a password if the server demands password authentication.
178 However,
<application>droplang
</application> will waste a
179 connection attempt finding out that the server wants a password.
180 In some cases it is worth typing
<option>-W<
/> to avoid the extra
192 <title>Environment
</title>
196 <term><envar>PGDATABASE
</envar></term>
197 <term><envar>PGHOST
</envar></term>
198 <term><envar>PGPORT
</envar></term>
199 <term><envar>PGUSER
</envar></term>
203 Default connection parameters
210 This utility, like most other
<productname>PostgreSQL<
/> utilities,
211 also uses the environment variables supported by
<application>libpq<
/>
212 (see
<xref linkend=
"libpq-envars">).
219 <title>Diagnostics
</title>
222 Most error messages are self-explanatory. If not, run
223 <application>droplang
</application> with the
<option>--echo
</option>
224 option and see under the respective
<acronym>SQL
</acronym> command
225 for details. Also, any default connection settings and environment
226 variables used by the
<application>libpq
</application> front-end
236 Use
<xref linkend=
"app-createlang"> to add a language.
242 <title>Examples
</title>
245 To remove the language
<literal>pltcl
</literal>:
247 <prompt>$
</prompt><userinput>droplang pltcl dbname
</userinput>
253 <title>See Also
</title>
255 <simplelist type=
"inline">
256 <member><xref linkend=
"app-createlang"></member>
257 <member><xref linkend=
"sql-droplanguage" endterm=
"sql-droplanguage-title"></member>