Re: I'd like to discuss scaleout at PGCon

From: Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: MauMau <maumau307(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: I'd like to discuss scaleout at PGCon
Date: 2018-06-07 05:25:21
Message-ID: CAFjFpRcYdX=dNJkiTMZsaXKJT3uZEU83Ssm66aARgqioLQwiuw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jun 7, 2018 at 10:53 AM, Michael Paquier <michael(at)paquier(dot)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(at)gmail(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Langote 2018-06-07 05:28:38 Re: Remove mention in docs that foreign keys on partitioned tables are not supported
Previous Message Michael Paquier 2018-06-07 05:23:10 Re: I'd like to discuss scaleout at PGCon