| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Corey Taylor <corey(dot)taylor(dot)fl(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: postgres 9.6: insert into select finishes only in pgadmin not psql |
| Date: | 2019-09-23 14:22:44 |
| Message-ID: | d4e25e56-3388-0684-d0b8-762b3ac6e700@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 9/23/19 12:07 AM, Corey Taylor wrote:
> First thing I'd look at is whether it's the same execution environment
> in both cases, eg same search_path.
>
>
> As far as I can tell, it's the same execution environment, same
> search_path and same user.
>
> I found after testing other situations, that the psql command would
> always finish as expected after canceling the first query that ran too
> long. I was able to reproduce this scenario with psql and pgadmin4 with
> various combinations.
>
> Any suggestions on what that would indicate? The canceled query does
> not complete as there are no rows and no duplicate errors when running
> the second time.
Can we see the actual function/query?
Also the schema of the table(s) involved?
>
> corey
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2019-09-23 14:36:38 | Re: How to get timezone offset in timestamp with time zone AT TIME ZONE output. |
| Previous Message | Pankaj Jangid | 2019-09-23 14:07:02 | Re: How to represent a bi-directional list in db? |