Re: WIP patch for parallel pg_dump - Mailing list pgsql-hackers

From Robert Haas
Subject Re: WIP patch for parallel pg_dump
Date
Msg-id AANLkTi=LpmeivefHLRFS-OXDUzf=HC5VZ4ttZwx3cnK4@mail.gmail.com
Whole thread Raw
In response to Re: WIP patch for parallel pg_dump  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: WIP patch for parallel pg_dump
List pgsql-hackers
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.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Timeout for asynchronous replication Re: Timeout and wait-forever in sync rep
Next
From: Alvaro Herrera
Date:
Subject: Re: FK's to refer to rows in inheritance child