Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id F08491337999 for ; Fri, 6 May 2011 20:24:02 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 48292-09 for ; Fri, 6 May 2011 23:23:45 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-wy0-f174.google.com (mail-wy0-f174.google.com [74.125.82.174]) by mail.postgresql.org (Postfix) with ESMTP id B1C271337B67 for ; Fri, 6 May 2011 20:23:44 -0300 (ADT) Received: by wya21 with SMTP id 21so2745120wya.19 for ; Fri, 06 May 2011 16:23:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type:content-transfer-encoding; bh=ulb1Nv3A/DF0z+ndLomlvlbqwfCfb+h7tqon4u1cgsY=; b=L6T30M3yuxK3Gz6vyukFxl7WQrFldJbPsUDADIFwwHn/j0JJtFYTzcGeVte9Lo/RD/ koef14a0dwU+lfS43fTSx9gN0lrIBc+qbkgoxF2TFKkK+ZLC+mXMcI/d/uVt3ym+Aq/C +Ua+DQXPMPn+Ez0wHsmva2LDO+rLHfjOKJGvo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=DClUgCt3gsNMjlLLrSusP5oq/1pUdTC+UuhL0dlm0scL/3kkFxc4dqs4gTli8ySaBN aCTZW+fXaWKM0y28qrKWrfj41ef/AEEI1f8N3WIagoXsRP+vy2vsi2IkXCpyD5tMi3Fd sOSRAefsS/JR8kDV37gUQdNFzT0HkmeL8wNlA= Received: by 10.216.246.74 with SMTP id p52mr54579wer.41.1304724224072; Fri, 06 May 2011 16:23:44 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.121.15 with HTTP; Fri, 6 May 2011 16:23:24 -0700 (PDT) In-Reply-To: <1304706536-sup-3669@alvh.no-ip.org> References: <1304702299.28821.1.camel@vanquo.pezone.net> <1304706536-sup-3669@alvh.no-ip.org> From: Josh Kupershmidt Date: Fri, 6 May 2011 19:23:24 -0400 Message-ID: Subject: Re: should pg_basebackup be listed as a server application? To: Alvaro Herrera Cc: Magnus Hagander , Peter Eisentraut , pgsql-docs Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.898 tagged_above=-5 required=5 tests=BAYES_00=-1.9, FREEMAIL_FROM=0.001, RFC_ABUSE_POST=0.001 X-Spam-Level: X-Archive-Number: 201105/24 X-Sequence-Number: 6699 On Fri, May 6, 2011 at 2:30 PM, Alvaro Herrera wrote: > Excerpts from Magnus Hagander's message of vie may 06 14:30:27 -0300 2011= : >> On Fri, May 6, 2011 at 19:18, Peter Eisentraut wrote: >> > The pg_basebackup reference page is currently under "Client >> > Applications" [0]. =A0I think it's more of a server application, becau= se >> > it's what you'd run instead of initdb on the server. =A0Should it be m= oved >> > to the "Server Applications" section? >> >> Not sure I buy that argument. pg_dump/pg_dumpall/pg_restore are under >> client applications. They're something you run *alongside* initdb and >> not instead, sure.. But they're all backup tools. > > Is there really a dichotomy here? Client/server? =A0Maybe we just need > another category, "administrative applications" or something like that. You can draw a clear line between applications which can connect to a server remotely, and those which need to be executed on the actual server machine, and thus distinguish "Client" from "Server" Applications. If we use that logic, I think pg_config should be listed as a "Server Application" and pg_basebackup should remain a "Client Application", and we'd be consistent. I think trying to break the Client Applications down into administrative and non-administrative isn't very helpful -- the only client applications I see which are clearly non-administrative (i.e. non-superusers would normally use) are psql and ecpg. Everything else seems like stuff you either generally need superuser privs for (create*, drop*, etc.) or are tools typically used by the server admin (taking and restoring backups). Josh