From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
---|---|
To: | Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> |
Cc: | Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: PoC/WIP: Extended statistics on expressions |
Date: | 2021-03-05 00:43:35 |
Message-ID: | 20210305004334.GR29832@telsasoft.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Jan 04, 2021 at 09:45:24AM -0600, Justin Pryzby wrote:
> On Mon, Jan 04, 2021 at 03:34:08PM +0000, Dean Rasheed wrote:
> > * I'm not sure I understand the need for 0001. Wasn't there an earlier
> > version of this patch that just did it by re-populating the type
> > array, but which still had it as an array rather than turning it into
> > a list? Making it a list falsifies some of the comments and
> > function/variable name choices in that file.
>
> This part is from me.
>
> I can review the names if it's desired , but it'd be fine to fall back to the
> earlier patch. I thought a pglist was cleaner, but it's not needed.
This updates the preliminary patches to address the issues Dean raised.
One advantage of using a pglist is that we can free it by calling
list_free_deep(Typ), rather than looping to free each of its elements.
But maybe for bootstrap.c it doesn't matter, and we can just write:
| Typ = NULL; /* Leak the old Typ array */
--
Justin
Attachment | Content-Type | Size |
---|---|---|
0001-bootstrap-convert-Typ-to-a-List.patchx | text/x-diff | 5.2 KB |
0002-Allow-composite-types-in-bootstrap.patchx | text/x-diff | 1.4 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Tomas Vondra | 2021-03-05 01:17:37 | Re: PoC/WIP: Extended statistics on expressions |
Previous Message | Hannu Krosing | 2021-03-05 00:38:02 | Re: Extensibility of the PostgreSQL wire protocol |