Re: pg_dump and thousands of schemas
Claudio Freire <klaussfreire@gmail.com>
From: Claudio Freire <klaussfreire@gmail.com>
To: Robert Klemme <shortcutter@googlemail.com>
Cc: Tatsuo Ishii <ishii@postgresql.org>, pgsql-performance@postgresql.org, pgsql-hackers@postgresql.org
Date: 2012-05-31T14:22:08Z
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 →
-
Teach AbortOutOfAnyTransaction to clean up partially-started transactions.
- 2755abf386e6 9.2.0 cited
On Thu, May 31, 2012 at 11:17 AM, Robert Klemme <shortcutter@googlemail.com> wrote: > > OK, my fault was to assume you wanted to measure only your part, while > apparently you meant overall savings. But Tom had asked for separate > measurements if I understood him correctly. Also, that measurement of > your change would go after the O(N^2) fix. It could actually turn out > to be much more than 9% because the overall time would be reduced even > more dramatic. So it might actually be good for your fix to wait a > bit. ;-) It's not clear whether Tom is already working on that O(N^2) fix in locking. I'm asking because it doesn't seem like a complicated patch, contributors may want to get working if not ;-)