Postgres Pro
Downloads
Home   >   mailing lists

Re: pg_dump --split patch - Mailing list pgsql-hackers

From Joel Jacobson
Subject Re: pg_dump --split patch
Date
Msg-id AANLkTimg=ZkbV8U5fd41fPhe1NCk_Xq-Daqw3963+ov-@mail.gmail.com
Whole thread Raw
In response to Re: pg_dump --split patch  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pg_dump --split patch  (Andrew Dunstan <andrew@dunslane.net>)
Re: pg_dump --split patch  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: pg_dump --split patch  (Aidan Van Dyk <aidan@highrise.ca>)
List pgsql-hackers
Tree view
2010/12/28 Tom Lane <tgl@sss.pgh.pa.us>

That has at least as many failure modes as the other representation.


I don't follow, what do you mean with "failure modes"? The oid in the filename? I suggested to use a sequence instead but you didn't comment on that. Are there any other failure modes which could cause a diff -r between two different databases to break?

(This might be a bad idea for some other reason, but I noticed a few other users requesting the same feature when I googled "pg_dump split".)

--
Best regards,

Joel Jacobson
Glue Finance

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pg_dump --split patch
Next
From: Teodor Sigaev
Date:
Subject: Re: knngist - 0.8