Re: createuser/dropuser username

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Susanne Ebrecht <susanne(at)2ndQuadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Grzegorz Szpetkowski <gszpetkowski(at)gmail(dot)com>, pgsql-docs(at)postgresql(dot)org
Subject: Re: createuser/dropuser username
Date: 2011-09-08 14:52:04
Message-ID: 201109081452.p88Eq4b02307@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > Tom Lane wrote:
> >> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> >>> It removes quoting for table references in clusterdb and index/table
> >>> references in reindexdb,
>
> >> Uh, surely that breaks things. Or did you miss my statement that the
> >> current behavior is what is intended?
>
> > I saw that, but how is that consistent with other command-line tools?
> > What is the logic that has some tools preserve case and others not?
>
> If there are any that fail to preserve case, those are the ones to be
> fixed. Making the working ones match the broken ones is not the correct
> direction.

I started going in that direction and stopped because of this example
in our docs:

vacuumdb --analyze --verbose --table 'foo(bar)' xyzzy

Ideas?

>
> > Really? Pg_dump doesn't preserve case for table names:
>
> > pg_dump -t Test test
>
> pg_dump is a special case because the arguments are patterns to match,
> not fixed names.

OK.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Alvaro Herrera 2011-09-08 15:11:50 Re: createuser/dropuser username
Previous Message Tom Lane 2011-09-08 14:40:31 Re: createuser/dropuser username