Hi
On Wed, Sep 12, 2018 at 10:12 AM, Johann Spies wrote:
> On Wed, Sep 12, 2018 at 09:05:37AM +0100, Dave Page wrote:
>
> > Can you provide logs? You may need to enable logging per
> > https://www.pgadmin.org/faq/#8.
>
> The log is complaining about not being able to contact the server on
> port
On Wed, Sep 12, 2018 at 09:05:37AM +0100, Dave Page wrote:
> Can you provide logs? You may need to enable logging per
> https://www.pgadmin.org/faq/#8.
The log is complaining about not being able to contact the server on
port 63334 (I am using a ssh tunnel not defined in pgadmin4).
The last part
On Wed, Sep 12, 2018 at 7:43 AM, jimmy wrote:
> I use pgAgent 3.4 in pgAdmin 4 to create a job. In this job I create a
> schedule and a step.
> I query the table pga_job, pga_jobagent, I find pga_job.jobagentid is null.
> That means it is not related with this schedule and step.
> How to operate
On Wed, Sep 12, 2018 at 8:18 AM, Johann Spies wrote:
> Apologies for the rant.
>
> When will we have a pgadmin that just works?
>
> I am on Debian Sid with a pgdg-installation (desktop) of pgadmin4.
>
> Today I cannot use it: "The application server could not be contacted."
>
> I have used it in
Apologies for the rant.
When will we have a pgadmin that just works?
I am on Debian Sid with a pgdg-installation (desktop) of pgadmin4.
Today I cannot use it: "The application server could not be contacted."
I have used it in the past with some frustration but it was usable.
Version: 3.3-1.pgd
