Re: [Postgres-xc-general] "Dropdb/Dropuser command not found" problem

On Wed, Oct 9, 2013 at 9:54 PM, Hector M. Jacas <hec...@et...>wrote:

>  Hi all,
>
> First I must apologize because obviously I was reading the document
> oriented to bash version of pgxc_ctl.
>
> In the documentation of the binary version there is no reference to these
> facilities (dropdb/dropuser). This is the one I should have read .
>
> My mistake and my apologies .
>
> I beg your patience and condescension when from the user role of this
> great project I take the liberty to comment the answer to my post .
>
> I do not share the view of Mr. Ashutosh Bapat when he says " is not an
> interface pgxc_ctl for dropping database or user. " reason: "It's just a
> cluster management utility "
>
> I think there is an inconsistency in that statement because the same
> reason for not including dropdb and dropuser commands are perfectly valid
> createdb and createuser .
>

There is difference between what is supported as a requirement and what is
supported because it fits well in the utility. You may compare pgxc_ctl
with pg_ctl, which basically allow controlling the life of server. pgxc_ctl
being made for XC, has to support life of a cluster and allows controlling
individual server. On top, it allows creating a cluster, (which is not
required in pg_ctl, initdb does it). This particular functionality needs
Createdb and Createuser, so does it support those. But a user should not
look at pgxc_ctl for managing individual databases. The server is more than
capable of doing it and that functionality can be accessed through
connectors or utilities like create* or drop*.


>
> You as project developers ( or contribution ) decide the philosophy with
> which your product works and I in my role as user I should be able to
> reconcile my working methods with the philosophy of the tools I have
> selected.
>
> POSTGRESXC is a great project because it solves big problems.
>
> PGXC_CTL is another great project because it simplifies the deployment and
> management of postgresxc and if you add shortcuts to frequently used
> commands (and perhaps, some security features) this project could become a
> kind of Central Command for POSTGRESXC .
>
> Thank you very much for your answers ,
>
> Hector M. Jacas
>
>
>
>
> On 10/09/2013 12:12 AM, Ashutosh Bapat wrote:
>
>  Hector,
>  AFAIK, pgxc_ctl is not an interface for dropping database or user. It's
> just a cluster management utility. You should use corresponding binaries or
> SQL commands for that purpose.
>
>
> On Tue, Oct 8, 2013 at 9:32 PM, Hector M. Jacas <hec...@et...>wrote:
>
>>
>> Hi all,
>>
>> Among the features described in:
>> https://github.com/koichi-szk/PGXC-Tools/blob/master/pgxc_ctl/manual.txtis deleting the databases (Dropdb) and users (Dropuser) and when I try make
>> use of these commands pgxc_ctl answers: command not found
>>
>> PGXC Createdb testdb
>> Selected coord2.
>> PGXC Dropdb testdb
>> sh: Dropdb: command not found
>> PGXC Createuser usertest1
>> Selected coord1.
>> PGXC Dropuser usertest1
>> sh: Dropuser: command not found
>> PGXC
>>
>> Carefully review the source code and found that in the folder:
>> postgres-xc/contrib/pgxc_ctl , there is a file (do_command.c) in which
>> reference is made and performed the execution of Createdb (line 2339) and
>> Createuser (line 2369).
>>
>> In this file there is no reference whatsoever to Dropdb or Dropuser .
>>
>> There is another file (in the same directory) called: pgxc_ctl.bash, in
>> which reference is made and run the corresponding command to Createdb,
>> Dropdb, Createuser and Dropuser.
>>
>> Do not remember reading during pgxc compliacion and deployment (or
>> pgxc_ctl in the area of contributions ) anything regarding how to handle
>> this situation.
>>
>> How to resolve this issue?
>>
>> The pgxc_ctl in its binary version lacks Dropdb and Dropuser commands?
>> I must choose between the binary version and the version bash? What would
>> be the impact of this change ?
>>
>> Can anyone guide me please
>>
>> Thanks in advance,
>>
>> Hector M. Jacas
>>
>> ---
>> This message was processed by Kaspersky Mail Gateway 5.6.28/RELEASE
>> running at host imx3.etecsa.cu
>> Visit our web-site: <http://www.kaspersky.com>, <http://www.viruslist.com
>> >
>>
>>
>> ------------------------------------------------------------------------------
>> October Webinars: Code for Performance
>> Free Intel webinars can help you accelerate application performance.
>> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most
>> from
>> the latest Intel processors and coprocessors. See abstracts and register >
>>
>> http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Postgres-xc-general mailing list
>> Pos...@li...
>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general
>>
>>
>
>
> --
> Best Wishes,
> Ashutosh Bapat
> EnterpriseDB Corporation
> The Postgres Database Company
>
>
> ---
> This message was processed by Kaspersky Mail Gateway 5.6.28/RELEASE running at host imx2.etecsa.cu
>
> Visit our web-site: <http://www.kaspersky.com> <http://www.kaspersky.com>, <http://www.viruslist.com> <http://www.viruslist.com>
>
>
>
> ---
> This message was processed by Kaspersky Mail Gateway 5.6.28/RELEASE
> running at host imx3.etecsa.cu
> Visit our web-site: <http://www.kaspersky.com>, <http://www.viruslist.com>
>
>


-- 
Best Wishes,
Ashutosh Bapat
EnterpriseDB Corporation
The Postgres Database Company