| From: | Dave Page <dpage(at)pgadmin(dot)org> |
|---|---|
| To: | Murtuza Zabuawala <murtuza(dot)zabuawala(at)enterprisedb(dot)com> |
| Cc: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
| Subject: | Re: PATCH: To fix the issue where cast function causes freeze (pgAdmin4) |
| Date: | 2016-07-15 11:07:45 |
| Message-ID: | CA+OCxowZ-UT5DDC-Dsbgp28e0vd8wLQTWoAH6ShVjK34OTFp+Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
On Thu, Jul 14, 2016 at 10:06 AM, Murtuza Zabuawala
<murtuza(dot)zabuawala(at)enterprisedb(dot)com> wrote:
> Hi,
>
> PFA patch to fix the issue where if user use cast function and it causes
> freeze in query tool.
> (RM#1438)
This fixes the hang, but then displays the wrong data type for the
first column - e.g.
SELECT CURRENT_TIMESTAMP, CAST ( CURRENT_TIMESTAMP AS text ) ;
will show the columns as "now text(8)" and "now text", when it should
be "now timestamp with time zone", "now text"
Note that SELECT CURRENT_TIMESTAMP also gets this a little wrong - it
shows "now timestamp with time zone(8)" (the size shouldn't be
included)
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2016-07-15 11:14:00 | pgAdmin 4 commit: Fix the issue in MATERIALIZED VIEW node where user wa |
| Previous Message | Dave Page | 2016-07-15 11:01:07 | Re: PATCH: To fix Timestamps displaying with time as 00:00 (pgAdmin4) |