Re: [GSoC] github repo and initial work

From: Charles Cui <charles(dot)cui1984(at)gmail(dot)com>
To: Aleksandr Parfenov <a(dot)parfenov(at)postgrespro(dot)ru>
Cc: Aleksander Alekseev <a(dot)alekseev(at)postgrespro(dot)ru>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Anastasia Lubennikova <a(dot)lubennikova(at)postgrespro(dot)ru>, Andrey Borodin <x4mmm(at)yandex-team(dot)ru>
Subject: Re: [GSoC] github repo and initial work
Date: 2018-05-25 15:08:43
Message-ID: CA+SXE9uPEgDvz20kLc+rw3DJtxzeWQ5tGNRJ5rXR+iQ+M6aF+w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Thanks for correcting me, will definitely study citext and see how a new
type is registered in plugin.

2018-05-24 23:23 GMT-07:00 Aleksandr Parfenov <a(dot)parfenov(at)postgrespro(dot)ru>:

> On Thu, 24 May 2018 18:25:28 -0700
> Charles Cui <charles(dot)cui1984(at)gmail(dot)com> wrote:
> > The second is to provide thrift type just like json or jsonb. When you
> > create a table, postgres knows ::thrift keywords.
> > I think method one should be easier to implement because it only
> > limits to this plugin. Method two needs modify postgres kernel to
> > register a new type, which may time consuming,
> > but more natural. Any ideas on this?
> >
> > Thanks, Charles
>
> Hi Charles,
>
> I prefer the second way with separate type. But I think it is good idea
> to wait for an answer from your project mentor or someone other.
>
> I'm not an expert in PostgreSQL user-defined types, but AFAIK, it
> doesn't require changes in PostgreSQL core, since types can be created
> in extensions. It doesn't require changes to grammar or something.
> You can look at citext contrib as an example.
>
> --
> Aleksandr Parfenov
> Postgres Professional: http://www.postgrespro.com
> Russian Postgres Company
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Charles Cui 2018-05-25 15:09:20 Re: [GSoC] github repo and initial work
Previous Message Robert Haas 2018-05-25 14:49:25 Re: Performance regression with PostgreSQL 11 and partitioning