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

Another backup q

From: Halford Dace <hdace(at)bluedot(dot)co(dot)za>
To: pgsql-admin(at)postgresql(dot)org
Subject: Another backup q
Date: 2001-01-11 11:10:08
Message-ID: Pine.LNX.4.10.10101111058230.1163-100000@orion.bluedot.co.za (view raw or flat)
Thread:
Lists: pgsql-admin
Hi all,

After a year or so of programming with it, I've become a serious Pg fan.

However, I have one quibble / query.

Many of my applications use large objects to store images, text chunks
etc. etc.  This works very well, and certainly has adequate performance
for anything I've ever tried to do with it.

However, what rather terrifies me is that pg_dump seems only to store the
oid field in the dump, and not the content of the LO itself.

(Oh, I'm using PostgreSQL 6.5.2 at the moment, but will be upgrading into
the 7.x range shortly).

Of course, I could write a program to back up the full content of any
given database, but right now I can't think of a generalised way to do
this for any given DB.

So, does anyone know a solution?  Or am I missing something?  I get
nervous having production DBs which I can't back up.

Regards,
Hal



Responses

pgsql-admin by date

Next:From: Thomas HellerDate: 2001-01-11 11:56:57
Subject: FATAL 1: Memory exhausted in AllocSetAlloc()
Previous:From: Ragnar KjørstadDate: 2001-01-11 08:03:36
Subject: Re: BAcking up a Postgres Database

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