Dropping extension left function behind about pg_bulkload

[dtseiler]

When I test from my sandbox, it does indeed remove the function:

postgres@postgres=# \sf+ pg_bulkload
ERROR:  function "pg_bulkload" does not exist
postgres@postgres=# create extension pg_bulkload;
CREATE EXTENSION
Time: 3.995 ms
postgres@postgres=# \sf+ pg_bulkload
        CREATE OR REPLACE FUNCTION public.pg_bulkload(options text[], OUT skip bigint, OUT count bigint, OUT parse_errors bigint, OUT duplicate_new bigint, OUT duplicate_old bigint, OUT system_time double precision, OUT user_time double precision, OUT duration double precision)
         RETURNS record
         LANGUAGE c
         STRICT
1       AS '$libdir/pg_bulkload', $function$pg_bulkload$function$
postgres@postgres=# drop extension pg_bulkload;
DROP EXTENSION
Time: 1.300 ms
postgres@postgres=# \sf+ pg_bulkload
ERROR:  function "pg_bulkload" does not exist

[dtseiler]

My assumption at this point was that the function was created from a SQL script and not via CREATE EXTENSION, and that it's safe to drop it manually at this point.

[dtseiler]

Ignore this. The pg_bulkload extension was only removed from one DB in the cluster, but not all.