pg.ddx.io  pgsql-pkg-debian@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Euler Taveira <euler@timbira.com.br>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Julien Rouhaud <rjuju123@gmail.com>
Cc: Tatsuo Ishii <ishii@sraoss.co.jp>
Cc: Chris Travers <chris.travers@adjust.com>
Cc: Andreas Karlsson <andreas@proxel.se>
Cc: Fred .Flintstone <eldmannen@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: PostgreSQL pollutes the file system
Date: Wed, 20 Mar 2019 15:08:32 -0300
Message-ID: <20190320180832.GA11614@alvherre.pgsql> (raw)
In-Reply-To: <CAHE3wggp=rsd6OcpZZ=1_r55AxK3G5MhZTX8_GV69ujCoRkJ7g@mail.gmail.com>

On 2019-Mar-20, Euler Taveira wrote:

> Em qua, 20 de mar de 2019 às 14:57, Tom Lane <tgl@sss.pgh.pa.us> escreveu:
> >
> > We managed to get rid of createlang and droplang in v10, and there
> > hasn't been that much push-back about it.  So maybe there could be
> > a move to remove createuser/dropuser?  Or at least rename them to
> > pg_createuser and pg_dropuser.  But I think this was discussed
> > (again) during the v10 cycle, and we couldn't agree to do more than
> > get rid of createlang/droplang.

Previous discussion: 
https://postgr.es/m/CABUevExPrfPH5K5qM=zsT7tvfyACe+i5qjA6bfWCKKYrh8MJLw@mail.gmail.com

> Votes? +1 to remove createuser/dropuser (and also createdb/dropdb as I
> said in the other email). However, if we don't have sufficient votes,
> let's at least consider a 'pg_' prefix.

I vote to keep these rename these utilities to have a pg_ prefix and to
simultaneously install symlinks for their current names, so that nothing
breaks.


[In a couple of releases we could patch them so that they print a
deprecation warning to stderr if they're invoked without the prefix.]

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services




view thread (113+ messages)  latest in thread

Message-ID: <20190320180832.GA11614@alvherre.pgsql>
Permalink:  ../20190320180832.GA11614@alvherre.pgsql/
Also on:    postgresql.org/message-id/20190320180832.GA11614@alvherre.pgsql

 · 

reply

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: alvherre@2ndquadrant.com, euler@timbira.com.br, tgl@sss.pgh.pa.us, rjuju123@gmail.com, ishii@sraoss.co.jp, chris.travers@adjust.com, andreas@proxel.se, eldmannen@gmail.com, pgsql-hackers@lists.postgresql.org
  Subject: Re: PostgreSQL pollutes the file system
  In-Reply-To: <20190320180832.GA11614@alvherre.pgsql>
  References: <CAHE3wggp=rsd6OcpZZ=1_r55AxK3G5MhZTX8_GV69ujCoRkJ7g@mail.gmail.com> <20190320180832.GA11614@alvherre.pgsql>

* 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