Skip to main content

Drop all Objects from Schema In Postgres

To Drop all objects from Postgres Schema there could be following two approaches:

  1. Drop Schema with cascade all and re-create it again. 
  2. In some cases where you dont want to/not allowed to drop and recreate schema, its easy to look for objects on current schema and drop them. following script would help to do so,
Create function which would do the task and then drop that function too.

---


CREATE OR REPLACE FUNCTION drop_DB_objects()
RETURNS VOID AS $$

DECLARE 
rd_object RECORD;
v_idx_statement VARCHAR(500);  

BEGIN

---1. Dropping all stored functions
RAISE NOTICE '%', 'Dropping all stored functions...';
FOR rd_object IN ( SELECT format('%I.%I(%s)', ns.nspname, p.proname, oidvectortypes(p.proargtypes)) as functionDef
    FROM pg_proc p 
   INNER JOIN pg_namespace ns ON (p.pronamespace = ns.oid)
   WHERE ns.nspname = current_schema
     AND p.proname <> 'drop_db_objects'
)
LOOP    

v_idx_statement = 'DROP FUNCTION ' || rd_object.functionDef;
RAISE NOTICE '%', v_idx_statement;
EXECUTE v_idx_statement;
END LOOP;
RAISE NOTICE '%', 'Done. Droped all stored functions...';
--2. Dropping all views
RAISE NOTICE '%', 'Dropping all views...';
FOR rd_object IN ( SELECT viewname 
    FROM pg_views 
   WHERE schemaname = current_schema
)
LOOP    
v_idx_statement = 'DROP VIEW ' || current_schema || '.' || rd_object.tablename;
RAISE NOTICE '%', v_idx_statement;
EXECUTE v_idx_statement;
END LOOP;
RAISE NOTICE '%', 'Done. Droped all views...';

--3. Dropping all table objects
RAISE NOTICE '%', 'Dropping all table objects...';
-- Drop child partitions first and then the base tables.
FOR rd_object IN (
with child as (
SELECT c.relname AS tablename, 0 as parent
FROM   pg_inherits 
JOIN   pg_class AS c ON (inhrelid=c.oid)
WHERE  c.relnamespace IN ( SELECT oid FROM   pg_namespace WHERE nspname = current_schema)
     )
select * from child
union all      
SELECT tablename, 1 as parent FROM pg_tables 
WHERE schemaname = current_schema
  AND tablename not in (select inn.tablename from child inn)
order by parent   
 )
LOOP

v_idx_statement = 'DROP TABLE ' || current_schema || '.' || rd_object.tablename;
RAISE NOTICE '%', v_idx_statement;
EXECUTE v_idx_statement;
END LOOP;
RAISE NOTICE '%', 'Done. Droped all table objects...';

--4. Dropping all Sequence objects
RAISE NOTICE '%', 'Dropping all Sequence objects...';
FOR rd_object IN ( SELECT sequence_name 
    FROM information_schema.sequences 
   WHERE sequence_schema = current_schema
)
LOOP    

v_idx_statement = 'DROP SEQUENCE ' || current_schema || '.' || rd_object.sequence_name;
RAISE NOTICE '%', v_idx_statement;
EXECUTE v_idx_statement;
END LOOP;
RAISE NOTICE '%', 'Done. Droped all sequences...';

END;
$$  LANGUAGE plpgsql;
 
SELECT * FROM drop_DB_objects();

DROP FUNCTION drop_DB_objects();

Comments

  1. Nice Article !
    This is my pleasure to read your article.
    Really this will help to people of PostgreSQL Server Community.

    I have also prepared one article about, Populate script to drop all functions in PostgreSQL.
    You can also visit my article, your comments and reviews are most welcome.

    http://www.dbrnd.com/2016/02/postgresql-populate-drop-function-script-with-the-type-of-parameters/

    ReplyDelete
  2. Thanks this helped a lot.

    ReplyDelete

Post a Comment

Popular posts from this blog

Distributed transaction in Oracle ( Over Oracle DBLink)

To fetch the data from one server to and other Oracle server over DBLink, I experienced the following facts of Oracle Distributed transactions: Security issue: -           We cannot create Public synonym for the remote object accessed over Private DBLink of other Database.   -           It’s allowed to create private synonym for remote object, but you cannot grant the access over this synonym to any other schema. If you try to provide the grants to other schema Oracle raises an error:              [ORA-02021: DDL operations are not allowed on a remote database] “In an all you can access remote objects over private DBLink in the same schema where DBLink is created”. Fetching the Ref Cursor at Remote site:                   Let’s say we have two site...

How to Troubleshoot Connectivity Issue with 11gR2 SCAN

I installed the Oracle 11g RAC successfully, But when tried connecting from remote client via SCAN, it used to raise ORA-12537. This is the most common issues that the happens with SCAN listener. And there are few common mistakes that generally  cause this issue. . So, here is how we can troubleshoot the connectivity issues with SCAN, and cases out the possibilities. 1)  Check if Local_listener and remote_listener parameter are set properly on all nodes. 2)  The very common issue is with permissions. SCAN will always be created under grid user (Grid cluserware installation user). Oracle will also create one local listener “LISTENER” during grid infrastructure installation. But if that is not present then always make sure that you create a local listener with grid user. This is required to handover the connection between remote and local listener. 3)  Also “oracle” executable should have given to oracle and grid user i.e. 6751.  Under $ORACLE_HOME/bi...