Igor Neyman wrote:
>
> Partition your MESSAGES table by week or month (read on table
> partitioning in PG docs).
>
> Pg_dump "old" purtitions from "current" server, when they are not needed
> any more.
> Move backups of dumped partitions to your "auxilary" server, and
> pg_restore them there.
H
Hi
Imagine I have used pg_dump to backup a given single schema.
Is there any feature in pg_restore (8.4) that would allow to restore this
schema in a schema with another name ?
Thanks
--
Christophe Doré
Hello
I came in this morning and noticed this warning sitting in my inbox quite a
few times...
WARNING: PD_ALL_VISIBLE flag was incorrectly set in relation "table_2010q1"
page 471118
WARNING: PD_ALL_VISIBLE flag was incorrectly set in relation "table_2010q1"
page 471119
WARNING: PD_ALL_VISIBLE
Christophe Dore writes:
Imagine I have used pg_dump to backup a given single schema.
Is there any feature in pg_restore (8.4) that would allow to restore this
schema in a schema with another name ?
I think there isn't. If the pg_dump is ASCII and the file is small enough
you could edit it.
Julio Leyva writes:
What about alter schema ?
How would that help?
If I understand correctly, the original poster is trying to do something
like:
Source DB
schema1.table1
And restore it to
schema2.table1
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes
Well, that would work if the schema, when restored, is free. If not, you'd like
to set the schema name in which you restore before restoring.
When you use Oracle, you can, using exp/imp, change the schema you restore in
by setting properly the program arguments. I understand that this is not
po
Hi,
I'm using PostgreSQL 8.2 on RedHat ES 5.
I connect to our database which is hosted remotely using PuTTY thro SSH
protocol.
As part of my maintenance activity, I was cloning the database using the
command:
CREATE DATABASE newdb WITH TEMPLATE=olddb;
While cloning was in-progress, my Interne
