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

From Kevin Grittner
Subject Re: WIP patch for parallel pg_dump
Date
Msg-id 4CFCD2E60200002500038351@gw.wicourts.gov
Whole thread Raw
In response to Re: WIP patch for parallel pg_dump  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: WIP patch for parallel pg_dump
List pgsql-hackers
Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> I'm still not convinced that using shared memory is a bad way to 
>> pass these around. Surely we're not talking about large numbers
>> of them.  What am I missing here?
> 
> They're not of a very predictable size.
Surely you can predict that any snapshot is no larger than a fairly
small fixed portion plus sizeof(TransactionId) * MaxBackends?  So,
for example, if you're configured for 100 connections, you'd be
limited to something under 1kB, maximum?
-Kevin


pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: Per-column collation
Next
From: Tom Lane
Date:
Subject: Re: serializable read only deferrable