Re: [ADMIN] pg_dumpall size

On Tue, Oct 21, 2008 at 11:56 AM, Marc Fromm <[EMAIL PROTECTED]> wrote: > I have the same postgresql databases on two different servers. > > Boteh servers have the same version of postgresql, 8.1. > > The following backup command creates a file twice as big on one server, > compared to the other se

Re: [ADMIN] PITR question with base backup

On Tue, Oct 21, 2008 at 2:29 PM, Scott Whitney <[EMAIL PROTECTED]> wrote: > It is, is it? I was completely under the impression that it was not. Don't > ask me where I got that impression. :) > > No problem whatsoever, in that case! > > Thanks for clearing up my inability to comprehend documentatio

Re: [ADMIN] pg_dumpall size twist

Marc Fromm <[EMAIL PROTECTED]> writes: > It turns out that one specific database called postgres is growing each time > I perform a restore from the pg_dumpall files. > The database postgres has gone from 5.1MB to 10MB to 15MB to 20MB. No other > database is growing like this. The pg_dumpall is u

Re: [ADMIN] PITR question with base backup

It is, is it? I was completely under the impression that it was not. Don't ask me where I got that impression. :) No problem whatsoever, in that case! Thanks for clearing up my inability to comprehend documentation... -Original Message- From: Alvaro Herrera [mailto:[EMAIL PROTECTE

Re: [ADMIN] PITR question with base backup

Scott Whitney wrote: > The problem is that I create databases pretty regularly. Let's say I create > 3 in a week. I'm not looking forward to going to my colo, grabbing the 20ish > GB tgz file and restoring it 3 times per week. I'd rather do that dance > monthly or quarterly and rely on the WALs in

[ADMIN] PITR question with base backup

I'm in the process of testing PITR recovery, and I have an issue. My "data" directory is 30GB. Not huge, but it certainly takes awhile to tar up. My understanding is: a) pg_start_backup b) tar up c) pg_stop_backup d) restore tar file The problem is that I create databases pretty regularly. Let's

[ADMIN] pg_dumpall size twist

I submitted a post about my pg_dumpall file being twice as big on one server compared to the other. It turns out that one specific database called postgres is growing each time I perform a restore from the pg_dumpall files. The database postgres has gone from 5.1MB to 10MB to 15MB to 20MB. No oth

Re: [ADMIN] oid2name

Isabella Ghiurea a écrit : > where can I download a copy of oid2name source code? It's available with PostgreSQL source code (http://www.postgresql.org/ftp/source/). -- Guillaume. http://www.postgresqlfr.org http://dalibo.com -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.or

Re: [ADMIN] oid2name

On Tue, 2008-10-21 at 10:45 -0700, Isabella Ghiurea wrote: > where can I download a copy of oid2name source code? > Isabella Grab the Postgres source for your version of choice. It's under the contrib/ directory. -- Brad Nicholson 416-673-4106 Database Administrator, Afilias Canada Corp.

[ADMIN] pg_dumpall size

I have the same postgresql databases on two different servers. Boteh servers have the same version of postgresql, 8.1. The following backup command creates a file twice as big on one server, compared to the other server. pg_dumpall -c -U postgres | gzip > alldb.gz Red Hat 5EL: alldb.gz is 29MB Fe

[ADMIN] oid2name

where can I download a copy of oid2name source code? Isabella -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin

Re: [ADMIN] Move tables to tablespace

Yes you can do this using following commands. For tables:- select ' alter table '||tablename||' set tablespace ;' from pg_tables where schemaname='' and tableowner='< mention table owner here >'; For index :- select ' alter index '||indexname||' set tablespace ;' from pg_indexes where schemanam