From: | Jeremy Thomason <jeremy(at)eco-teknica(dot)com> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: import job not working |
Date: | 2019-08-26 20:22:28 |
Message-ID: | e445ad6f-bd18-de17-3598-2384ca3f6fc4@eco-teknica.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
here goes:
1) yes, import/export feature
2) the normal sequence for this process is a job notification, then a
progress window, then completion notification. It is not progressing
beyond the job notification
3) no idea
4) nothing I could find
What I could find elsewhere on google is that people have resolved this
by reverting to PgAdmin 3.
On 26/08/2019 11:04, Adrian Klaver wrote:
> On 8/26/19 9:00 AM, Jeremy Thomason wrote:
>> I have been trying to find a reason and a solution for import not
>> working for DBs on Azure, localhost and Aiven. The import dialogue
>> results in a job-created notification and nothing more. It is odd as
>> it used to work and am not sure what has changed. I am using
>> PGAdmin4.12 on Win10
>
> This is going to need more information:
>
> 1) Are you using some feature of pgAdmin?
>
> 2) If all it does is create a notification why is it an import?
>
> 3) What is the actual code?
>
> 4) Have you looked at the Postgres logs to see if there is anything
> relevant?
>
>>
>>
>>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2019-08-26 21:25:04 | Re: Postgres SQLSTATE[08006] [7] timeout expired |
Previous Message | Howard Wells | 2019-08-26 20:07:15 | Re: Postgres SQLSTATE[08006] [7] timeout expired |