Hi
On Wed, Jan 9, 2019 at 1:37 AM Patrick De Visschere
wrote:
> Dave,
>
> Thanks but this is my ~/Library/Preferences/org.pgadmin.pgadmin4.plist
> with the Browser command filled in
> (I have removed the content of the data tags)
>
>
> http://www.apple.com/DTDs/PropertyList-1.0.dtd";>
>
>
>
Looks like a firewall or pg_hba.conf issue, probably the 5433 is open to
pgadmin4 client but not 5434.
En 9 de enero de 2019 14:14:19 Mark Steben
escribió:
Good morning,
I am running pgadmin4 (3.5) We currently run postgres 9.4.8 in our
production environments
I have a linux server running
Good morning,
I am running pgadmin4 (3.5) We currently run postgres 9.4.8 in our
production environments
I have a linux server running two instances of postgres 9.4. One listens
on port 5433 and one listens on port 5434. I can login to the instance on
5433 but not on 5434, receiving this error:
On Wed, 9 Jan 2019, 19:00 Petr Fedorov Thanks - it helped!
>
Please keep the support mail group in the loop.
Thanks,
Murtuza
>
> 09.01.2019 15:42, Murtuza Zabuawala пишет:
>
>
> Hi,
>
> On Tue, Jan 8, 2019 at 3:59 PM Petr Fedorov
> wrote:
>
>> Hello,
>>
>> I'm using pgAdmin 4 version 3.6 on Cen
Nanina,
If you can do it through the psql prompt, then the problem is most likely
pgAdmin4, otherwise you might want to get in touch with the postgreSQL
devs/support lists.
For example, you can run the COPY command both with and without the HEADERS
option and see if that works.
I hope that helps
Hi,
On Tue, Jan 8, 2019 at 3:59 PM Petr Fedorov
wrote:
> Hello,
>
> I'm using pgAdmin 4 version 3.6 on Centos 7, Postgresql 10.6 runs on the
> same machine. I use local connections.
>
> Almost everything works fine except for 'Statistics' tab when viewing
> pgAgent job log. It takes 60-90 second
Hi,
thanks for trying. Yes the backup included the invalid data, but we've just
found the problem.
The 'special' characters in the data are handled just fine, but not if they are
present in the column names.
So does pgAdmin handle both data differently or is it Postgres? I thought if
the db
Hi
On Wed, Jan 9, 2019 at 3:29 PM Nanina Tron wrote:
>
> Hi,
> thanks for trying. Yes the backup included the invalid data, but we've just
> found the problem.
> The 'special' characters in the data are handled just fine, but not if they
> are present in the column names.
> So does pgAdmin hand
