pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ireneusz Pluta <ipluta@wp.pl>
To: Lukas <lukas@fmf.vtu.lt>
Cc: pgsql-novice@postgresql.org
Cc: pgsql-admin@postgresql.org
Subject: Re: Pg_dump and bytaA
Date: Fri, 09 Mar 2007 16:18:49 +0100
Message-ID: <45F17AD9.1080507@wp.pl> (raw)
In-Reply-To: <53561.85.206.198.223.1173384127.squirrel@fmf.vtu.lt>
References: <53561.85.206.198.223.1173384127.squirrel@fmf.vtu.lt>

Lukas napisaƂ(a):
> Hello,
>
>  we have one table in database (db has over 200 tables), which has one
> byteA filed for storing user photos. We are making backup every night, but
> it is now too large because of photos. We do not need to make backup of
> photos every night, but the question is how to backup database without
> this field?
>  I tried to look at keys of pgdump, but found nothing...
>
> Now we are using it like this:
> pg_dump -f /home/backup/DB.sql -d -Fp -v DB
>
> thx
> Lukas
>
>   
A different idea:

Why don't you move your photos table to a dedicated schema? Then you can 
dump only main schema, not including the photos schema, with the -n 
option to pg_dump. So, assuming that 'public' is the schema where all 
your other tables exist, your command would look like:

pg_dump -n public -f /home/backup/DB.sql -d -Fp -v DB

If you then change your mind and find that you need photos dump too, but 
possibly on a schedule different from the rest, you may be dumping only 
photos schema with something like:

pg_dump -n photos -f /home/backup/photos.sql -d -Fp -v DB

however you might want a different output format (compressed?) in this case.

Of course, this change would require you to make your application know 
where the photos table is. But most probably this can be easily done by 
executing something like "SET search_path TO photos, public", just after 
each connection to your database.

Irek.




view thread (13+ messages)  latest in thread

Message-ID: <45F17AD9.1080507@wp.pl>
Permalink:  ../45F17AD9.1080507@wp.pl/
Also on:    postgresql.org/message-id/45F17AD9.1080507@wp.pl

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: ipluta@wp.pl, lukas@fmf.vtu.lt, pgsql-novice@postgresql.org
  Subject: Re: Pg_dump and bytaA
  In-Reply-To: <45F17AD9.1080507@wp.pl>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox