Horton

Re: [HACKERS] pg_dump and thousands of schemas

Andrew Dunstan <andrew@dunslane.net>

View thread
From: Andrew Dunstan <andrew@dunslane.net>
To: Denis <socsam@gmail.com>
Cc: pgsql-performance@postgresql.org
Date: 2012-11-14T03:56:16Z
Lists: pgsql-hackers, pgsql-performance

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Teach AbortOutOfAnyTransaction to clean up partially-started transactions.

On 11/13/2012 10:12 PM, Denis wrote:
> Please don't think that I'm trying to nitpick here, but pg_dump has options
> for dumping separate tables and that's not really consistent with the idea
> that "pg_dump is primarily  designed for dumping entire databases".
>
>


Sure it is. The word "primarily" is not just a noise word here.

The fact that we have options to do other things doesn't mean that its 
primary design goal has changed.


cheers

andrew