Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bXb56-0002hO-C7 for pgsql-docs@arkaria.postgresql.org; Wed, 10 Aug 2016 21:30:32 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bXb55-0006Ph-V9 for pgsql-docs@arkaria.postgresql.org; Wed, 10 Aug 2016 21:30:32 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bXb4j-0005YK-7b for pgsql-docs@postgresql.org; Wed, 10 Aug 2016 21:30:09 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bXb4f-0003ZL-4j for pgsql-docs@postgresql.org; Wed, 10 Aug 2016 21:30:08 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id u7ALU3h8029016; Wed, 10 Aug 2016 17:30:04 -0400 From: Tom Lane To: ken.zito@tmctechnologies.com cc: pgsql-docs@postgresql.org Subject: Re: Admin catalog setup In-reply-to: <20160810154817.1427.75320@wrigleys.postgresql.org> References: <20160810154817.1427.75320@wrigleys.postgresql.org> Comments: In-reply-to ken.zito@tmctechnologies.com message dated "Wed, 10 Aug 2016 15:48:17 -0000" Date: Wed, 10 Aug 2016 17:30:03 -0400 Message-ID: <29015.1470864603@sss.pgh.pa.us> X-Pg-Spam-Score: -2.4 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-docs Precedence: bulk Sender: pgsql-docs-owner@postgresql.org ken.zito@tmctechnologies.com writes: > Page: https://www.postgresql.org/docs/9.2/static/adminpack.html > Description: > This is the script shown on the website: > int8 pg_catalog.pg_file_write(fname text, data text, append bool) > bool pg_catalog.pg_file_rename(oldname text, newname text, archivename text) > bool pg_catalog.pg_file_rename(oldname text, newname text) > bool pg_catalog.pg_file_unlink(fname text) > setof record pg_catalog.pg_logdir_ls() > /* Renaming of existing backend functions for pgAdmin compatibility */ > int8 pg_catalog.pg_file_read(fname text, data text, append bool) > bigint pg_catalog.pg_file_length(text) > int4 pg_catalog.pg_logfile_rotate() My goodness, that's an embarrassingly bad excuse for actual documentation, isn't it. I'm surprised this has been there so long and no one's tried to improve it. Maybe I will. > It states that it should be run as a superuser. I am new to postgresql. I > ran these step because I will be using pgadmin3. I ran the scripts in psql > as myself who is a superuser. I got nothing back from these commands. How > can I check if it ran correctly? It didn't, because those are just function prototypes not SQL commands. (If you'd added a semicolon at the end, you'd have gotten a syntax error, but if you didn't then psql is probably still waiting for you to complete the command.) What you are supposed to do to install adminpack, these days, is say "CREATE EXTENSION adminpack;". FWIW, though I'm not at all familiar with pgAdmin, I'd have guessed that it could/would do this for you. regards, tom lane -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs