Re: pg_dump --split patch
Alvaro Herrera <alvherre@2ndquadrant.com>
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Marko Tiikkaja <pgmail@joh.to>
Cc: Dimitri Fontaine <dimitri@2ndQuadrant.fr>, Joel Jacobson <joel@trustly.com>, pgsql-hackers@postgresql.org
Date: 2012-11-28T18:46:48Z
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
Marko Tiikkaja wrote: > On 16/11/2012 15:52, Dimitri Fontaine wrote: > > > >What happens if you have a table foo and another table "FoO"? > > They would go to the same file. If you think there are technical > issues behind that decision (e.g. the dump would not restore), I > would like to hear an example case. create table foo (a int, b text); create type bar as (stuff foo); create table "FoO" (more bar); -- Álvaro Herrera http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services