Re: Optimze usage of immutable functions as relation

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: rmrodriguez(at)carto(dot)com
Cc: Anastasia Lubennikova <a(dot)lubennikova(at)postgrespro(dot)ru>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Optimze usage of immutable functions as relation
Date: 2019-09-24 15:17:11
Message-ID: 19228.1569338231@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

rmrodriguez(at)carto(dot)com writes:
> This commit is breaking some Postgis tests with custom types.

Hm, yeah, the code fails to consider the possibility that the function
returns a composite type.

For the moment I'm just going to make it punt if the function result
class isn't TYPEFUNC_SCALAR. In principle, if we have a composite
result, we could disassemble it into per-column constant values, but
I'm not sure it'd be worth the work.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Nikolay Shaplov 2019-09-24 15:20:31 Re: [PATCH] src/test/modules/dummy_index -- way to test reloptions from inside of access method
Previous Message Alvaro Herrera 2019-09-24 15:13:07 Re: PostgreSQL12 and older versions of OpenSSL