Re: Arrays of domain returned to client as non-builtin oiddescribing the array, not the base array type's oid

Поиск
Список
Период
Сортировка
От Alvaro Herrera
Тема Re: Arrays of domain returned to client as non-builtin oiddescribing the array, not the base array type's oid
Дата
Msg-id 201901041924.hu6jvjqfdp46@alvherre.pgsql
обсуждение исходный текст
Ответ на Arrays of domain returned to client as non-builtin oid describing thearray, not the base array type's oid  (James Robinson <james@jlr-photo.com>)
Ответы Re: Arrays of domain returned to client as non-builtin oid describing the array, not the base array type's oid  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
On 2019-Jan-02, James Robinson wrote:

> So -- do others find this inconsistent, or is it just me and I should
> work on having psycopg2 be able to learn the type mapping itself if I
> don't want to do SQL-side casts? I'll argue that if scalar projections
> erase the domain's oid, then array projections ought to as well.

Sounds reasonable.

Do you have a link to a previous discussion that rejected changing the
returned OID to that of the domain array?  I want to know what the argument
is, other than backwards compatibility.

Disregarding the size/shape of a patch to change this, I wonder what's
the cost of the change.  I mean, how many clients are going to be broken
if we change it?  And by contrast, how many apps are going to work
better with array-on-domain if we change it?

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Peter Geoghegan
Дата:
Сообщение: Re: Making all nbtree entries unique by having heap TIDs participatein comparisons
Следующее
От: Alvaro Herrera
Дата:
Сообщение: Re: Use atexit() in initdb and pg_basebackup