"SunWuKung" <[EMAIL PROTECTED]> writes:
> The way I found out that I have to create language before and set the
> searchpath after running restore is that I found that the restored db
> doesn't work - which was quite scary at first.
You should not need to create the language --- that *is* part of
I think there should be an easier way to backup a single database and
restore it on another server.
In my case we are developing a db so there are many schema changes to
that. When there is a significant change we find it easier to drop and
recreate the db from the backup - withouth affecting the
Tom Lane wrote:
Richard Huxton writes:
True enough, but I'd think you could make a good argument that dumping a
database should dump any ALTER commands that are attached to it.
Let's suppose pg_dump did that, so "pg_dump foo >foo.dump" includes
commands like
ALTER DATABASE foo SET ..
Richard Huxton writes:
> True enough, but I'd think you could make a good argument that dumping a
> database should dump any ALTER commands that are attached to it.
Let's suppose pg_dump did that, so "pg_dump foo >foo.dump" includes
commands like
ALTER DATABASE foo SET ...
Now what hap
Brandon Aiken wrote:
PostgreSQL is simply very granular about what it lets you dump.
True enough, but I'd think you could make a good argument that dumping a
database should dump any ALTER commands that are attached to it.
Users are shared between databases, so I can see it doesn't necessari
12, 2006 3:19 AM
To: pgsql-general@postgresql.org
Subject: Re: [GENERAL] search_path when restoring to new db
Ok, I understand this difference now.
Knowing that, what is the standard way to copy a single database to
another server?
- can I use pg_dumpall to dump a single db? - or
- I have to use pg
Ok, I understand this difference now.
Knowing that, what is the standard way to copy a single database to
another server?
- can I use pg_dumpall to dump a single db? - or
- I have to use pg_dump and there is a procedure to ensure that old and
new dbs are the same, like
1. create new db
2. check o
56 PM
To: pgsql-general@postgresql.org
Subject: Re: [GENERAL] search_path when restoring to new db
Thanks for your answers.
I guess it means that I have to issue Alter database after restore
than.
I find this a little scary because this is something that I just
realised now and wouldn't hav
Thanks for your answers.
I guess it means that I have to issue Alter database after restore
than.
I find this a little scary because this is something that I just
realised now and wouldn't have thought beforehand. Seems to me that to
make an exact copy of a single db it isn't enough to use pg_back
On Mon, 2006-12-11 at 10:06, Tom Lane wrote:
> "SunWuKung" <[EMAIL PROTECTED]> writes:
> > It seems to me that if I dump and restore a database as a new db I need
> > to manually issue
> > ALTER DATABASE dbname SET search_path=schema1, schema2;
> > to get back the search_path of the original db.
>
"SunWuKung" <[EMAIL PROTECTED]> writes:
> It seems to me that if I dump and restore a database as a new db I need
> to manually issue
> ALTER DATABASE dbname SET search_path=schema1, schema2;
> to get back the search_path of the original db.
ALTER DATABASE and ALTER USER commands are handled by pg
It seems to me that if I dump and restore a database as a new db I need
to manually issue
ALTER DATABASE dbname SET search_path=schema1, schema2;
to get back the search_path of the original db. I
s this realy the case or I am doing something wrong and there is a way
to have the backup-restore do t
12 matches
Mail list logo
