Skip site navigation (1) Skip section navigation (2)

Re: Backup of entire servers and roles/tablespaces

From: "Hiroshi Saito" <z-saito(at)guitar(dot)ocn(dot)ne(dot)jp>
To: "Dave Page" <dpage(at)postgresql(dot)org>,"pgadmin-hackers" <pgadmin-hackers(at)postgresql(dot)org>
Subject: Re: Backup of entire servers and roles/tablespaces
Date: 2007-01-05 16:56:30
Message-ID: 01ef01c730ea$72850830$01324d80@hiroshi5jz7dqj (view raw, whole thread or download thread mbox)
Lists: pgadmin-hackers

> I'm just in the process of hacking pgAdmin to allow backup of entire
> servers or global info (roles and tablespaces). I was using the same
> mechanism as we use for pg_dump, however this doesn't work with
> pg_dumpall which doesn't support the -f option to redirect output to a file.
> Instead, I've been looking at separating the output and error streams
> from pg_dumpall, however this won't work either because pg_dumpall calls
> pg_dump to do much of it's work, and we cannot attach to those streams
> through pg_dumpall.
> I'm therefore toying with writing our own backup code to act as an
> equivalent to pg_dumpall, but would really prefer not to do this as the
> backup code is extremely important to get right of course.
> Thoughts or ideas?

Yea, I think so. however, surely the importance exists for a user.
I know that it has many problems with pgpass.conf....
Although only a specific user may be able to save, pgAdmin3 does 
not have preparations in it. probably, it is desirable. 

Hiroshi Saito

In response to

pgadmin-hackers by date

Next:From: Guillaume LelargeDate: 2007-01-05 17:10:32
Subject: Re: Backup of entire servers and
Previous:From: Devrim GUNDUZDate: 2007-01-05 16:55:03
Subject: Re: Backup of entire servers and

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group