The following bug has been logged online:

Bug reference: 1893
Logged by: Daniel Naschenweng
Email address: daniel.blumenau (AT) gmail (DOT) com
PostgreSQL version: 8.1 beta2
Operating system: Windows
Description: pg_dumpall - Search path order
Details:

When PostgreSQL make pg_dumpall, it set the search_path before a schema
create.
The import error:
NOTICE: schema "usuario1" does not exist

--
-- PostgreSQL database cluster dump
--

\connect postgres

--
-- Roles
--

CREATE ROLE usuario1 WITH NOSUPERUSER INHERIT NOCREATEROLE NOCREATEDB
LOGIN;
ALTER ROLE usuario1 SET search_path TO usuario1, public, pg_catalog;
CREATE ROLE usuario2 WITH NOSUPERUSER INHERIT NOCREATEROLE NOCREATEDB
LOGIN;
ALTER ROLE usuario2 SET search_path TO usuario2, public, pg_catalog;
CREATE ROLE usuario3 WITH NOSUPERUSER INHERIT NOCREATEROLE NOCREATEDB
LOGIN;
ALTER ROLE usuario3 SET search_path TO usuario3, public, pg_catalog;

(...)

--
-- Name: usuario1; Type: SCHEMA; Schema: -; Owner: usuario1
--

CREATE SCHEMA usuario1;

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo (AT) postgresql (DOT) org so that your
message can get through to the mailing list cleanly

"Daniel Naschenweng" <daniel.blumenau (AT) gmail (DOT) com> writes:
This is not an error, it's only a notice.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings