Re: pg_dump --split patch
Joel Jacobson <joel@gluefinance.com>
From: Joel Jacobson <joel@gluefinance.com>
To: pgsql-hackers@postgresql.org
Date: 2010-12-28T16:59:31Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
pg_dump: Output functions deterministically sorted
- 7b583b20b1c9 9.3.0 cited
-
When sorting functions in pg_dump, break ties (same name) by number of arguments
- 1acc06a1f4ae 9.0.0 cited
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