From: | Ondrej Ivanič <ondrej(dot)ivanic(at)gmail(dot)com> |
---|---|
To: | Hugo <hugo(dot)tech(at)gmail(dot)com> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: pg_dump and thousands of schemas |
Date: | 2012-05-25 05:12:43 |
Message-ID: | CAM6mieLLpi80RhqcJ_njSBnwSg1ognxq=D5hLP5eQFSh29VmOw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-performance |
Hi,
On 25 May 2012 14:54, Hugo <Nabble> <hugo(dot)tech(at)gmail(dot)com> wrote:
> Thanks for the replies. The number of relations in the database is really
> high (~500,000) and I don't think we can shrink that. The truth is that
> schemas bring a lot of advantages to our system and postgresql doesn't show
> signs of stress with them. So I believe it should also be possible for
> pg_dump to handle them with the same elegance.
>
> If anyone has more suggestions, I would like to hear them. Thank you!
Maybe filesystem level backup could solve this issue:
http://www.postgresql.org/docs/9.1/static/continuous-archiving.html#BACKUP-BASE-BACKUP
but keep in mind that:
- it preserves bloat in your database thus backup might need more space
- you can't restore to different PG version
--
Ondrej Ivanic
(ondrej(dot)ivanic(at)gmail(dot)com)
From | Date | Subject | |
---|---|---|---|
Next Message | Karl Schnaitter | 2012-05-25 06:56:01 | patch: Use pg_mbcliplen for truncation in text-to-name conversion |
Previous Message | Hugo <Nabble> | 2012-05-25 04:54:05 | Re: pg_dump and thousands of schemas |
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Spiegelberg | 2012-05-25 11:58:38 | Re: Maximum number of sequences that can be created |
Previous Message | Hugo <Nabble> | 2012-05-25 04:54:05 | Re: pg_dump and thousands of schemas |