pt templates and dump
> >them out.
> That is pretty neat! Here is Gavin's script slighty modified with some
> extra features useful to me and maybe to you, too:
Thanks a lot. This is really nice.
--
Cheers,
Jacob Atzen
---(end of broadcast)--
.4.5:
% pg_dumpall -O
pg_dumpall: invalid option -- O
But I'll just use pg_dump where it does exist.
--
Thanks,
Jacob Atzen
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
is
> "PostgreSQL Client Applications" - it covers all the options.
> I'd use pg_dump anyway - unless you have hundreds of databases, it makes
> it easier to keep by backups separate.
I will do that then. Thanks.
--
Cheers,
Jacob Atzen
---(end of
On Fri, Jun 17, 2005 at 01:13:16PM +0100, Raymond O'Donnell wrote:
> On 17 Jun 2005 at 13:52, Jacob Atzen wrote:
> > The second problem is a matter of database ownership. Apparently
> > pg_dumpall will dump the owners of the database along with the data.
> > This is cau
quot;pgsql" but on my local machine the
name is "postgres". How do I get around this? Should I just abandon
pg_dumpall and use pg_dump instead or is there some other way?
--
Thanks,
Jacob Atzen
---(end of broadcast)---
TIP 1: subscri
