On Fri, Aug 26, 2016 at 5:42 PM, Peter Eisentraut
wrote:
> On 8/26/16 12:26 PM, Euler Taveira wrote:
>> initdb: we already have 'pg_ctl init' (since 9.0) and could remove initdb.
>
> I have a concern specifically about pg_ctl. Depending on how your
> PostgreSQL is packaged, not all of the pg_ctl
On 8/26/16 12:26 PM, Euler Taveira wrote:
> initdb: we already have 'pg_ctl init' (since 9.0) and could remove initdb.
I have a concern specifically about pg_ctl. Depending on how your
PostgreSQL is packaged, not all of the pg_ctl actions are safe or
sensible to run. For example, if you are usin
On 2016-08-26 13:26:39 -0300, Euler Taveira wrote:
> I'm bringing this $subject into discussion again. Historically, we are
> carrying binary names that have been confused newbies. createuser is the
> worst name so for. Also, names like createdb, initdb, reindexdb, and
> droplang does not suggest w
On Fri, Aug 26, 2016 at 04:33:47PM -0300, Euler Taveira wrote:
> On 26-08-2016 14:03, David Fetter wrote:
> > Would these make sense as pg_ctl options, or are you separating them
> > out because they're not instance-wide? If separating them is
> > important on those grounds, how about something li
On 08/26/2016 07:03 PM, David Fetter wrote:
On Fri, Aug 26, 2016 at 01:26:39PM -0300, Euler Taveira wrote:
Hi,
...
>>
initdb: we already have 'pg_ctl init' (since 9.0) and could remove initdb.
Opinions?
+1 for removing initdb.
We can't just remove it because pg_ctl actually calls initdb
Simon Riggs wrote:
> On 26 August 2016 at 18:26, Euler Taveira wrote:
>
> > I'm bringing this $subject into discussion again. Historically, we are
> > carrying binary names that have been confused newbies. createuser is the
> > worst name so for. Also, names like createdb, initdb, reindexdb, and
On 2016-08-26 15:03, Andres Freund wrote:
On 2016-08-26 22:01:58 +0200, Simon Riggs wrote:
On 26 August 2016 at 18:26, Euler Taveira
wrote:
> I'm bringing this $subject into discussion again. Historically, we are
> carrying binary names that have been confused newbies. createuser is the
> wor
On 2016-08-26 22:01:58 +0200, Simon Riggs wrote:
> On 26 August 2016 at 18:26, Euler Taveira wrote:
>
> > I'm bringing this $subject into discussion again. Historically, we are
> > carrying binary names that have been confused newbies. createuser is the
> > worst name so for. Also, names like cre
On 26 August 2016 at 18:26, Euler Taveira wrote:
> I'm bringing this $subject into discussion again. Historically, we are
> carrying binary names that have been confused newbies. createuser is the
> worst name so for. Also, names like createdb, initdb, reindexdb, and
> droplang does not suggest w
On 26-08-2016 14:03, David Fetter wrote:
> Would these make sense as pg_ctl options, or are you separating them
> out because they're not instance-wide? If separating them is
> important on those grounds, how about something like pg_db or
> pg_db_command?
>
It doesn't make sense because pg_ctl is
On Fri, Aug 26, 2016 at 01:26:39PM -0300, Euler Taveira wrote:
> Hi,
>
> I'm bringing this $subject into discussion again. Historically, we are
> carrying binary names that have been confused newbies. createuser is the
> worst name so for. Also, names like createdb, initdb, reindexdb, and
> dropla
Hi,
I'm bringing this $subject into discussion again. Historically, we are
carrying binary names that have been confused newbies. createuser is the
worst name so for. Also, names like createdb, initdb, reindexdb, and
droplang does not suggest what product it is referring to. Adding a
prefix (pg_,
12 matches
Mail list logo
