AW: Proposal: More flexible backup/restore via pg_dump

From: Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at>
To: "'Philip Warner'" <pjw(at)rhyme(dot)com(dot)au>, pgsql-hackers(at)postgresql(dot)org
Subject: AW: Proposal: More flexible backup/restore via pg_dump
Date: 2000-06-26 08:17:05
Message-ID: 219F68D65015D011A8E000006F8590C605BA598C@sdexcsrv1.f000.d0188.sd.spardat.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> The broad approach would be modify the existing pg_dump as little as
> possible; I am inclined to write the data as SQL (as currently done), and
> append an 'index' to the output, specifying the offset on the file that
> each piece of extractable data can be found. The 'restore' option would
> just go to the relevant section(s), and pipe the data to psql.

A problem I see with an index at file end is, that you will need to read the
file
twice, and that may be very undesireable if e.g the backup is on tape
or a compressed file.

I like your idea of uniquely formatted comments heading separate sections
of the dump file, if the "create table ..." is not already enough.

Andreas

Browse pgsql-hackers by date

  From Date Subject
Next Message Zeugswetter Andreas SB 2000-06-26 09:31:06 AW: Big 7.1 open items
Previous Message Zeugswetter Andreas SB 2000-06-26 08:09:13 File versioning (was: Big 7.1 open items)