Re: second post: pg_dump and revision control - Mailing list pgsql-general
From | Joshua b. Jore |
---|---|
Subject | Re: second post: pg_dump and revision control |
Date | |
Msg-id | Pine.BSO.4.44.0206040856130.7022-100000@kitten.greentechnologist.org Whole thread Raw |
In response to | Re: second post: pg_dump and revision control (Peter Dimov <jquest_j@yahoo.com>) |
List | pgsql-general |
It think it should be clear by now that the revision control (RC) is not an artifact of PostgreSQL; this fact is reflected in the absence of documentation for this on http://www.postgresql.org/idocs. From the perspective of PostgreSQL all of the RC stuff is really just vanilla database schema - the RC is just additional tables, views, etc. You stated in one of your original messages that you used PgAdmin II. Look at *that* to see what design elements were added. Your key here is to either remove those from your database thus deleting your RC system or to work around it. pg_dump will extract either individual elements or everything. This just works to say - either the "users" table or every table. So your dump strategy might be to inventory your design elements and extract each thing individually. Of course retain the data from your tables as well. So now assume you have a borked output file from pg_dump/pg_dumpall and now you just want to restore the data. First be clear on what style file you created. You use pg_restore only with the compressed and tar output formats and only then to recreate a plaintext SQL script. That SQL script is then fed to psql as input and the theory says that it all goes correctly. So at this point you edit your SQL script to remove the odd bits and you monitor PostgreSQL's operation during the load to see which constructs are causing the errors. You must start from the beginning since later constructs may depend on something that went by earlier. Joshua b. Jore ; http://www.greentechnologist.org ; 1121 1233 1311 200 1201 1302 1211 200 1201 1303 200 1300 1233 1313 1211 1302 1212 1311 1230 200 1201 1303 200 1321 1233 1311 1302 200 1211 1232 1211 1231 1321 200 1310 1220 1221 1232 1223 1303 200 1321 1233 1311 200 1201 1302 1211 232 200 1112 1233 1310 1211 200 1013 1302 1211 1211 1232 201 22 On Tue, 4 Jun 2002, Peter Dimov wrote: > > Hi, > many thanks for the answer. > I did it and in my log I see many messages as: > " Object restored from Revision Log (Version 0). > 2002-04-23 08:39:26-04 myuser A Table test 2784641 1 > CREATE TABLE "test" (\ > "ids" varchar(20)\ > ); > \ > > " > > > I think it is clear that the problem is in the revision control. > > The question is: How to disable this revision control by data import and/or by data export? > > I readet the docs but don't find any info about it. > > > > Many thanks. > > > Stephan Szabo <sszabo@megazone23.bigpanda.com> wrote: > > On Mon, 3 Jun 2002, Peter Dimov wrote: > > > > > Hi all, > > > > I am using postgresql 7.2 on linux and if I try to make > > > > pg_dump, the system generate a big dump file. > > > > I think it depend on revision control on my database. > > > > If it is so how can I dump my data without this revision control? > > You had said trying to reload gave parser errors. I'd suggest > turning on query logging to see what the queries erroring are > as a first step. > > > > > ---------------------------(end of broadcast)--------------------------- > TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org > > > > --------------------------------- > Do You Yahoo!? > Sign-up for Video Highlights of 2002 FIFA World Cup
pgsql-general by date: