| From: | Joe Conway <mail(at)joeconway(dot)com> |
|---|---|
| To: | Piotr Findeisen <piotr(dot)findeisen(at)starburstdata(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Is _<typename> a supported way to create a column of array type? |
| Date: | 2019-04-26 12:15:51 |
| Message-ID: | e52f6e8c-4a4e-00f9-9ee7-ea89bef474fc@joeconway.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 4/26/19 6:50 AM, Piotr Findeisen wrote:
> Presto type system however distinguishes array(integer),
> array(array(integer))...
> (using Presto therms). And execution is (expectedly) not as flexible.
Fine point here -- Postgres does not actually have arrays-of-arrays, it
has multi-dimension arrays.
So in other words, you cannot have an array of element type _int4, but
rather you literally have an array of element type int4 with two
dimension, etc..
Joe
--
Crunchy Data - http://crunchydata.com
PostgreSQL Support for Secure Enterprises
Consulting, Training, & Open Source Development
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Wildish | 2019-04-26 12:25:54 | Re: Inexplicable UPDATE...RETURNING behaviour |
| Previous Message | Piotr Findeisen | 2019-04-26 10:50:01 | Re: Is _<typename> a supported way to create a column of array type? |