From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Greg Smith <greg(at)2ndquadrant(dot)com>, Joachim Wieland <joe(at)mcknight(dot)de>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: WIP patch for parallel pg_dump |
Date: | 2010-12-06 15:35:56 |
Message-ID: | 4CFD02DC.1070705@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 12/06/2010 10:22 AM, Robert Haas wrote:
> On Mon, Dec 6, 2010 at 9:58 AM, Heikki Linnakangas
> <heikki(dot)linnakangas(at)enterprisedb(dot)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
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2010-12-06 15:38:13 | Re: WIP patch for parallel pg_dump |
Previous Message | Andrew Chernow | 2010-12-06 15:33:02 | Re: Suggesting a libpq addition |