Re: Resolve UNKNOWN type to relevant type instead of text type while bulk update using values

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Sayyid Ali Sajjad Rizavi <sasrizavi(at)gmail(dot)com>
Cc: "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Resolve UNKNOWN type to relevant type instead of text type while bulk update using values
Date: 2023-01-05 06:23:24
Message-ID: CAKFQuwbtoPA5_LKd+j=Kc3XoFOaobyRgcFDfpj24jD=KFPhF6A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wednesday, January 4, 2023, Sayyid Ali Sajjad Rizavi <sasrizavi(at)gmail(dot)com>
wrote:
>
>
> *Option 1:* Cast to the relevant column type in that position (to
> `integer` in this case), whenever we have an unknown type.
>

This happens when possible so any remaining cases are not possible. Or, at
least apparently not worth the effort it would take to make work.

> *Option 2:* Always give error if unknown type is not casted to desired
> type (`null::integer` will be necessary).
>

Breaking working queries for this is not acceptable.

David J.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Sayyid Ali Sajjad Rizavi 2023-01-05 06:30:39 Re: Resolve UNKNOWN type to relevant type instead of text type while bulk update using values
Previous Message Masahiko Sawada 2023-01-05 06:15:41 Re: Fix showing XID of a spectoken lock in an incorrect field of pg_locks view.