Robert Treat <[EMAIL PROTECTED]> writes:
> I can't be the only one forsee frustration from users who typo the set
> search_path statement and then can't figure out why their tables aren't
> showing up... can we emit a warning that not all of the schemas in the
> search path were found?
Since no o
2004 19:16:47 -0500
> > From: Tom Lane <[EMAIL PROTECTED]>
> > To: [EMAIL PROTECTED]
> > Cc: pgsql-hackers list <[EMAIL PROTECTED]>,
> > Peter Eisentraut <[EMAIL PROTECTED]>
> > Subject: Re: [HACKERS] set search_path and pg_dumpall
> >
>
D]
> Cc: pgsql-hackers list <[EMAIL PROTECTED]>,
> Peter Eisentraut <[EMAIL PROTECTED]>
> Subject: Re: [HACKERS] set search_path and pg_dumpall
>
> [EMAIL PROTECTED] writes:
> > When a serch_path has been set, pg_dumpall correctly output a alter
> > database
[EMAIL PROTECTED] writes:
> When a serch_path has been set, pg_dumpall correctly output a alter
> database xxx set search_path to 'xxx' but *BEFORE* the schema is created
> so it doesn't work.
Hm. It's worse than that really: in ALTER DATABASE SET, we are trying
to check the search path in the wr
Hi all,
Still trying to upgrade from 7.3.4 to 7.4.1 with pg_dumpall.
2 problemes:
When a serch_path has been set, pg_dumpall correctly output a alter
database xxx set search_path to 'xxx' but *BEFORE* the schema is created
so it doesn't work.
And about my previous mails, if I pg_dump the databas
