Re: XTM & parallel search

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Konstantin Knizhnik <k(dot)knizhnik(at)postgrespro(dot)ru>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: XTM & parallel search
Date: 2016-06-03 13:05:30
Message-ID: CAA4eK1KtfgVZtwu0ttVsxAG+WjYuR913fipk+62PsqN+ETpkBw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Jun 3, 2016 at 1:34 AM, Konstantin Knizhnik <
k(dot)knizhnik(at)postgrespro(dot)ru> wrote:

> We have to add three more functions to eXtensible Transaction Manager API
> (XTM):
>
> /*
> * Calculate transaction state size. This method is invoked by
> EstimateTransactionStateSpace to copy transaction
> * state to parallel workers
> */
> size_t (*GetTransactionStateSize)(void);
>
> /*
> * Serialize transaction state
> */
> void (*SerializeTransactionState)(void* ctx);
>
> /*
> * Deserialize transaction state
> */
> void (*DeserializeTransactionState)(void* ctx);
>
>

In above proposal, are you suggesting to change the existing API's as well,
because the parameters of function pointers don't match with exiting API's.
I think it is better to consider this along with the overall XTM API.

With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Konstantin Knizhnik 2016-06-03 13:19:13 Re: XTM & parallel search
Previous Message Robert Haas 2016-06-03 12:34:47 Re: Rename max_parallel_degree?