Re: CREATE TABLE creates a composite type corresponding to the table row, which is and is not there

From: Erik Wienhold <ewie(at)ewie(dot)name>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: Hannu Krosing <hannuk(at)google(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: CREATE TABLE creates a composite type corresponding to the table row, which is and is not there
Date: 2024-04-04 04:41:19
Message-ID: efxy4vnyrwhowyyv7vk6s7ps6bwkyizdmaehs7mppjzapssvxl@n5nuyelnyfcj
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2024-04-04 03:29 +0200, David G. Johnston wrote:
> On Thu, Mar 28, 2024 at 8:02 PM Erik Wienhold <ewie(at)ewie(dot)name> wrote:
>
> > Thanks, that sounds better. I incorporated that with some minor edits
> > in the attached v3.
> >
>
> You added my missing ( but dropped the comma after "i.e."

Thanks, fixed in v4. Looks like American English prefers that comma and
it's also more common in our docs.

--
Erik

Attachment Content-Type Size
v4-0001-Document-that-typed-tables-rely-on-CREATE-TYPE.patch text/plain 3.6 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Davis 2024-04-04 04:54:48 Re: Improve eviction algorithm in ReorderBuffer
Previous Message Bharath Rupireddy 2024-04-04 04:34:02 Re: Introduce XID age and inactive timeout based replication slot invalidation