Re: I'd like to discuss scaleout at PGCon - Mailing list pgsql-hackers

From Ashutosh Bapat
Subject Re: I'd like to discuss scaleout at PGCon
Date
Msg-id CAFjFpRcYdX=dNJkiTMZsaXKJT3uZEU83Ssm66aARgqioLQwiuw@mail.gmail.com
Whole thread Raw
In response to Re: I'd like to discuss scaleout at PGCon  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
On Thu, Jun 7, 2018 at 10:53 AM, Michael Paquier <michael@paquier.xyz> wrote:
> On Thu, Jun 07, 2018 at 10:28:15AM +0530, Ashutosh Bapat wrote:
>> On Wed, Jun 6, 2018 at 8:16 PM, MauMau <maumau307@gmail.com> wrote:
>>> Looking at the XL source code, the following sequence of functions are
>>> called when the coordinator handles the Row Description message ('T')
>>> from the data node.  I guess the parsing is necessary to process type
>>> names combined with type modifiers, e.g. "char(100)".
>>>
>>>     create_tuple_desc
>>>     parseTypeString
>>>     typeStringToTypeName
>>>     raw_parser
>>
>> Hmm, strange. I had not seen that in Postgres-XC.
>
> Where is that located in the XC code?  If you point out to the location
> it may revive some past memories from either Ashutosh or me.

I think the path will exist in XC as well since that's regular
PostgreSQL path, but I didn't see it being a hot path in XC. So, we
will need to find the workload/cases where it's a hot path.

> --
> Michael



-- 
Best Wishes,
Ashutosh Bapat
EnterpriseDB Corporation
The Postgres Database Company


pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: I'd like to discuss scaleout at PGCon
Next
From: Amit Langote
Date:
Subject: Re: Remove mention in docs that foreign keys on partitioned tablesare not supported