| From: | Steve Rogerson <steve(dot)pg(at)yewtc(dot)demon(dot)co(dot)uk> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: postgres 11 issue? |
| Date: | 2019-07-05 11:18:56 |
| Message-ID: | ef35f12c-ed6d-2aa5-4bcc-12acbcab08a1@yewtc.demon.co.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 03/07/2019 20:36, Tom Lane wrote:
>
> It looks like what's happening is that the result of my_from_local()
> is being stored into the table as an anonymous record value rather
> than a value of type my_timestamp. (The originating session can figure
> out what the anonymous record type is, but no other session can.)
> That should be fixed, but in the meantime you could dodge the problem by
> declaring my_from_local()'s v_result variable as my_timestamp not record.
>
Thanks for the quick response. The "workaround" works, though it would seem
best practice in any case.
Steve
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PegoraroF10 | 2019-07-05 11:38:54 | Re: Converting to identity columns with domains on PK columns |
| Previous Message | Andrey Sychev | 2019-07-05 09:39:03 | Re: Error: rows returned by function are not all of the same row type |