From: Christoph Berg <myon@debian.org>
To: Joe Conway <mail@joeconway.com>
Cc: Pavel Stehule <pavel.stehule@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Andres Freund <andres@anarazel.de>
Cc: Tatsuo Ishii <ishii@sraoss.co.jp>
Cc: Andreas Karlsson <andreas@proxel.se>
Cc: Tomas Vondra <tomas.vondra@2ndquadrant.com>
Cc: eldmannen@gmail.com, mark.kirkwood@catalyst.net.nz, Michael Paquier <michael@paquier.xyz>
Cc: Chris Travers <chris.travers@adjust.com>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Euler Taveira <euler@timbira.com.br>
Cc: rjuju123@gmail.com, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: PostgreSQL pollutes the file system
Date: Fri, 29 Mar 2019 20:43:30 +0100
Message-ID: <20190329194330.GD19154@msg.df7cb.de> (raw)
In-Reply-To: <48e5efaf-7ea2-ed70-a803-949bbfec8f6b@joeconway.com>
References: <375ea28a-2e8c-9954-66b1-bd0a3ff657f5@proxel.se>
<18182.1553697687@sss.pgh.pa.us>
<20190329.100407.1159785913847835944.t-ishii@sraoss.co.jp>
<20190329152557.GI20294@msg.df7cb.de>
<24256.1553874086@sss.pgh.pa.us>
<20190329155121.5zyoahgh4i2r4ayl@alap3.anarazel.de>
<19517.1553876700@sss.pgh.pa.us>
<20190329185031.GA19154@msg.df7cb.de>
<CAFj8pRAFpZcDGL5i1wMQiHZ43y5Qd=22=+2vTCFOrak_mrUxjw@mail.gmail.com>
<48e5efaf-7ea2-ed70-a803-949bbfec8f6b@joeconway.com>
Re: Joe Conway 2019-03-29 <48e5efaf-7ea2-ed70-a803-949bbfec8f6b@joeconway.com>
> echo "\password :\"role\"" | psql -v role='my role'
> Enter new password:
> Enter it again:
>
> That said, this is kind of off the topic of this thread.
It is on-topic because the reason we can't just tell people to replace
createuser $foo
with
psql -c "create user $foo"
is because $foo might need escaping.
IMHO if we find an way to do that which is acceptable for sh scripts,
the createuser/... commands could go.
> I like Tom's last suggestion of:
>
> pg_util <command> <options>
>
> Of course that does not lend itself to symlinking for backward
> compatibility, does it? If there is a way I am not familiar with it.
We could symlink createuser -> pg_util. It is pretty common for
commands to act differently based on the name the were invoked as.
> I guess the alternative would be an alias, but can packages install an
> alias? Or something else I am not thinking about?
Aliases won't work for non-interactive shell scripts.
Christoph
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-pkg-debian@postgresql.org
Cc: myon@debian.org, mail@joeconway.com, pavel.stehule@gmail.com, tgl@sss.pgh.pa.us, andres@anarazel.de, ishii@sraoss.co.jp, andreas@proxel.se, tomas.vondra@2ndquadrant.com, michael@paquier.xyz, chris.travers@adjust.com, alvherre@2ndquadrant.com, euler@timbira.com.br, pgsql-hackers@lists.postgresql.org
Subject: Re: PostgreSQL pollutes the file system
In-Reply-To: <20190329194330.GD19154@msg.df7cb.de>
References: <375ea28a-2e8c-9954-66b1-bd0a3ff657f5@proxel.se> <18182.1553697687@sss.pgh.pa.us> <20190329.100407.1159785913847835944.t-ishii@sraoss.co.jp> <20190329152557.GI20294@msg.df7cb.de> <24256.1553874086@sss.pgh.pa.us> <20190329155121.5zyoahgh4i2r4ayl@alap3.anarazel.de> <19517.1553876700@sss.pgh.pa.us> <20190329185031.GA19154@msg.df7cb.de> <CAFj8pRAFpZcDGL5i1wMQiHZ43y5Qd=22=+2vTCFOrak_mrUxjw@mail.gmail.com> <48e5efaf-7ea2-ed70-a803-949bbfec8f6b@joeconway.com> <20190329194330.GD19154@msg.df7cb.de>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox