On Wed, 18 May 2005, Tom Lane wrote:
Oleg Bartunov writes:
unfortunately, no, because I deleted dump file. But, I just tried to
reproduce my problem with 8.0.3 and got no problem. I think, I tried
dump from 7.4.
Possibly it was just that 7.4's pg_dump isn't bright enough about dump
order? I can't
Oleg Bartunov writes:
> unfortunately, no, because I deleted dump file. But, I just tried to
> reproduce my problem with 8.0.3 and got no problem. I think, I tried
> dump from 7.4.
Possibly it was just that 7.4's pg_dump isn't bright enough about dump
order? I can't think of any other 7.4-to-8.0
On Wed, 18 May 2005, Tom Lane wrote:
Oleg Bartunov writes:
any problem in restore. Unfortunately, pg_dump explicitly defines
search path to 'public, pg_catalog' and any objects from 'contrib' schema
doesn't seen, which cause many errors, for example, table uses type tsvector,
which defined in tsea
Oleg Bartunov writes:
> any problem in restore. Unfortunately, pg_dump explicitly defines
> search path to 'public, pg_catalog' and any objects from 'contrib' schema
> doesn't seen, which cause many errors, for example, table uses type tsvector,
> which defined in tsearch2 module, so that table do
Hi there,
I got a problem playing with schema and dump/restore process (8.0.3).
I created schema 'contrib' for my database and added it to search_path
in postgresql.conf. Then I loaded a bunch of modules to 'contrib schema' and
populated database with various tables. Everything is ok, I could dump
