Re: WIP patch for parallel pg_dump
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>, Tom Lane <tgl@sss.pgh.pa.us>, Greg Smith <greg@2ndquadrant.com>, Joachim Wieland <joe@mcknight.de>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2010-12-06T15:38:13Z
Lists: pgsql-hackers
On Mon, Dec 6, 2010 at 10:35 AM, Andrew Dunstan <andrew@dunslane.net> wrote: > On 12/06/2010 10:22 AM, Robert Haas wrote: >> >> On Mon, Dec 6, 2010 at 9:58 AM, Heikki Linnakangas >> <heikki.linnakangas@enterprisedb.com> wrote: >>> >>> On 06.12.2010 15:53, Robert Haas wrote: >>>> >>>> I guess. It still seems far too much like exposing the server's guts >>>> for my taste. It might not be as bad as the expression tree stuff, >>>> but there's nothing particularly good about it either. >>> >>> Note that we already have txid_current_snapshot() function, which exposes >>> all that. >> >> Fair enough, and I think that's actually useful for Slony&c. But I >> don't think we should shy away of providing a cleaner API here. >> > > Just don't let the perfect get in the way of the good :P I'll keep that in mind. :-) -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company