s know.
>
> On Sat, Jul 11, 2020 at 2:03 PM Suzanne Ronayne
> wrote:
>
>> Hello. Is there any way I could find a copy of the .exe file for
>> pgadmin3?
>>
>> I am running Windows 7, SP1, 32-bit, and I get an error message when I
>> try to install pgadmin4
for
> pgadmin3?
>
> I am running Windows 7, SP1, 32-bit, and I get an error message when I try
> to install pgadmin4 x86.exe or x64.exe that says the system "cannot access
> 64-bit registry keys". Pgadmin is supposed to be available for Windows 7,
> according to this
Hello. Is there any way I could find a copy of the .exe file for pgadmin3?
I am running Windows 7, SP1, 32-bit, and I get an error message when I try to
install pgadmin4 x86.exe or x64.exe that says the system "cannot access 64-bit
registry keys". Pgadmin is supposed to be ava
Hi,
This morning, upgrading pgadmin3 from the "apt.postgresql.org"
repository leads to install a new version
(pgadmin3_1.22.2-6.pgdg18.04+1_amd64.deb) over the previous one
(pgadmin3_1.22.2-5.pgdg18.04+1_amd64.deb).
Now, when pgAdmin3 is launched, it crashes whenever the "SQL
9, at 11:40 PM, Praveen Agarwal
> wrote:
>
> Hi Team,
>
> I'm in dire need of help.
> I was using pdgamin3 on macOS, recently after upgrading to macOS-Catalina,
> pgadmin3 along with other apps are banned, I have set lot of important
> queries in favourti
Hi Team,
I'm in dire need of help.
I was using pdgamin3 on macOS, recently after upgrading to macOS-Catalina,
pgadmin3 along with other apps are banned, I have set lot of important
queries in favourties, since its not opening now, is there a way these
favourites queries can be export from f
couple of bugs, mainly due to browser integration, which
have not been fixed and probably never will.
Regards
From: Nikita Kiryanov [mailto:nik...@compulab.co.il]
Sent: mercredi 6 février 2019 09:42
To: pgadmin-support@lists.postgresql.org
Subject: pgadmin3 incredibly slow over network
-support@lists.postgresql.org
Subject: RE: pgadmin3 incredibly slow over network
Can you run an explain query in both? And copy the results...
__
Saludos
Ing. Ricardo Martín Gomez
DBA - SysAdmin
_
De: Nikita Kiryanov mailto:nik...@compulab.co.il> >
E
in-support@lists.postgresql.org
Asunto: RE: pgadmin3 incredibly slow over network
Hi Ricardo,
I tried to reverse the order (first HeidiSQL then pgAdmin), but the result was
the same.
From: Ricardo Martin Gomez [mailto:rimartingo...@hotmail.com]
Sent: Wednesday, February 6, 2019 12:43 PM
To: Nikita Kiryanov
Hi Ricardo,
I tried to reverse the order (first HeidiSQL then pgAdmin), but the result was
the same.
From: Ricardo Martin Gomez [mailto:rimartingo...@hotmail.com]
Sent: Wednesday, February 6, 2019 12:43 PM
To: Nikita Kiryanov ;
pgadmin-support@lists.postgresql.org
Subject: RE: pgadmin3
Admin
De: Nikita Kiryanov
Enviado: miércoles, 6 de febrero de 2019 05:42
Para: pgadmin-support@lists.postgresql.org
Asunto: pgadmin3 incredibly slow over network
If I use pgAdmin3 to query a remote database with SELECT * FROM big_table, the
whole thing takes 1.5 minutes un
If I use pgAdmin3 to query a remote database with SELECT * FROM big_table, the
whole thing takes 1.5 minutes until I get my results.
If I run the same query, from the same computer, to the same remote database,
using a different client (HeidiSQL, or even pgsql), it
takes 5 seconds.
I run
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,
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
ing to SQ:_ASCII
> means is that postgreSQL *won't *do any translations between character
> encoding for you. We are storing what I believe is Windows-1252 characters
> in the database. The immediate problem (at least mine in so far as
> pgAdmin4 is concerned) is that non-UTF8 char
between character encoding for you.
> We are storing what I believe is Windows-1252 characters in the database.
> The immediate problem (at least mine in so far as pgAdmin4 is concerned) is
> that non-UTF8 characters (like smart quotes) are handled without a problem by
> psql, .Net,
cters (like smart quotes) are
handled *without* a problem by psql, .Net, and Windows ODBC (and under
pgAdmin3) but cause pgAdmin4 to crash/fail/thow errors. The only way to
get pgAdmin4 to behave is to locate and remove the offending characters.
My guess is that this is due to it's python underpi
ll have to periodically scan and clean for bad UTF8 data
>> > to keep pgAdmin4 (and other JDBC dependent code) happy. The legacy
>> > enterprise .Net applications that depend on it prohibit converting it to
>> > UTF8 (or anything else for that matter).
>> >
>>
On Tue, Jan 8, 2019 at 8:55 PM Nanina Tron wrote:
>
>
> Hi,
>
> yes thank you I will scan the table so at least I will see the 'bad'
> characters. We will see how many there are.
> Sorry, i forgot to append the data.
Thanks. Did that include the "bad" data? I can load it just fine into
a SQL_ASC
Hi
On Tue, Jan 8, 2019 at 7:32 PM richard coleman
wrote:
>
> Dave,
>
> I would imagine Nanina would be in a better position to provide you with
> problematic import/export data in the short term. I don't tend to
> import/export that often these days, preferring to use SQL statements for
> mos
nderstand from your explanations is that I imported kind of invalid
data with pgAdmin3 to begin with and now can't copy these tables in pgAdmin4
because psql has a problem with it? If so why can't I import a new .csv file in
UTF8 into an new created table with pgAdmin4? I just have one op
res
> ENCODING = 'UTF8'
> LC_COLLATE = 'de_DE.UTF-8'
> LC_CTYPE = 'de_DE.UTF-8'
> TABLESPACE = pg_default
> CONNECTION LIMIT = -1;
>
> So what I understand from your explanations is that I imported kind of
> invalid data with pgAdmi
Dave,
I would imagine Nanina would be in a better position to provide you with
problematic import/export data in the short term. I don't tend to
import/export that often these days, preferring to use SQL statements for
most things short of a full backup/restore (in my case I've found it to be
muc
Hi Rik
On Tue, Jan 8, 2019 at 6:53 PM richard coleman
wrote:
>
> Dave,
>
> Thanks for continuing this discussion, but I think you misunderstand the
> situation. I am storing valid non-UTF8 data in a SQL_ASCII encoded
> postgreSQL database (please re-read what I had previously written). This is
t matter).
> >
> > Just my $0.02,
> >
> > rik.
> >
> >
> > On Mon, Jan 7, 2019 at 1:27 PM Dave Page wrote:
> >>
> >> Hi
> >>
> >> On Mon, Jan 7, 2019 at 11:30 PM richard coleman
> >> wrote:
> >> >
>
; Hi
>>
>> On Mon, Jan 7, 2019 at 11:30 PM richard coleman
>> wrote:
>> >
>> > Dave,
>> >
>> > I can't speak to Nania's specific issue, but I believe it's a pgAdmin4
>> > specific problem, at least in so far as SQL_ASCI
ta just fine from the psql prompt,
> but not through pgAdmin4 (or other postgreSQL GUI's like dBeaver that rely
> on the JDBC connection). .Net/Windows ODBC drivers and psql command
> prompt, no problem (as was pgAdmin3 assuming you don't do too much with it
> beyond select/upd
ta just fine from the psql prompt, but
> not through pgAdmin4 (or other postgreSQL GUI's like dBeaver that rely on the
> JDBC connection). .Net/Windows ODBC drivers and psql command prompt, no
> problem (as was pgAdmin3 assuming you don't do too much with it beyond
> sele
's like dBeaver that rely on the JDBC
connection). .Net/Windows ODBC drivers and psql command prompt, no problem
(as was pgAdmin3 assuming you don't do too much with it beyond
select/update/insert). pgAdmin4, SELECT, export, etc. *BOOM*! At least
until you *cleaned * up the offending by
]
>> )[89ab][0-9a-f]
>> )*(..)?
>> $r$, '-\1-', 'g')
>> $BODY$;
>> ALTER FUNCTION live.badutf8(text)
>> OWNER TO postgres;
>
>
> Fixes bad UTF8
>
>
>
> On Mon, Jan 7, 2019 a
tgres;
Fixes *bad* UTF8
On Mon, Jan 7, 2019 at 8:40 AM Nanina Tron wrote:
> Hi,
>
> I am pretty new to PostgreSQL so I might just miss something basic here.
>
> My problem is that, I cannot import or export some of the tables in my db
> with pgAdmin4, as it raises the “E
imported via pgAdmin3.
The strange thing is that it can still be imported and exported with pgAdmin3
but not with pgAdmin4. The db was created with encoding UTF-8, the .csv files
where created with encoding UTF-8 and also the import/export dialog is set to
UTF-8. Queries are also no problem on
Doug,
Agreed. I've looked for BigSQL's build of pgAdmin3 on their web site but
have only found it bundled with their installer, which would be fine if it
allowed you to deselect BigSQL itself. How are you installing it? Could you
kindly provide a link to the correct page of their sit
Mojave is just saying that the NEXT MacOS version coming out in a year will
require 64bit apps. This is a nag. But if you want to keep using PgAdmin3,
Apple will still be releasing security updates for Mojave for the next 3 years
so you have that long to still be fully patched with it
gt;>
>>> +1 - thanks for the heads-up, Bill. I was just about to upgrade, but I
>>> guess I’ll hold off until they respond to this request.
>>>
>>>
>>>> On Nov 5, 2018, at 8:50 AM, Bill Evans >>> <mailto:b...@literacybridge.org>&g
gt;> I’ll hold off until they respond to this request.
>>
>>
>>> On Nov 5, 2018, at 8:50 AM, Bill Evans >> <mailto:b...@literacybridge.org>> wrote:
>>>
>>> Hello,
>>>
>>> I recently upgraded my Mac to the latest version of
One addition:
Pgadmin3 works fine on macOS Mojave. But it will not run at all on some future
version of macOS. Safe to upgrade; the message is annoying at worst. (But it is
a bit annoying.)
Best,
-bill
From: "Strauch, Sheldon"
Date: Monday, November 5, 2018 at 10:05
,
>>
>> I recently upgraded my Mac to the latest version of macOS. Now, when I run
>> pgadmin3, I get a message that it needs to be recompiled, apparently for
>> 64bit.
>>
>> Is there a plan to rebuild pgadmin3 for macOS Mojave?
>>
>>
AM, Bill Evans wrote:
>
> Hello,
>
> I recently upgraded my Mac to the latest version of macOS. Now, when I run
> pgadmin3, I get a message that it needs to be recompiled, apparently for
> 64bit.
>
> Is there a plan to rebuild pgadmin3 for macOS Mojave?
>
> I know you’r
+1 - thanks for the heads-up, Bill. I was just about to upgrade, but I guess
I’ll hold off until they respond to this request.
> On Nov 5, 2018, at 8:50 AM, Bill Evans wrote:
>
> Hello,
>
> I recently upgraded my Mac to the latest version of macOS. Now, when I run
>
Hello,
I recently upgraded my Mac to the latest version of macOS. Now, when I run
pgadmin3, I get a message that it needs to be recompiled, apparently for 64bit.
Is there a plan to rebuild pgadmin3 for macOS Mojave?
I know you’re rather bullish on #4, but it still isn’t up the the
Hi Rolf,
New version of pgAdmin is available - pgAdmin4
Kindly visit - https://www.pgadmin.org/
On Sun, Aug 26, 2018 at 11:51 PM Rolf Brandt wrote:
> pgadmin3 startet nicht in Netrunner OS (Arch Linux)
>
> Mit freundlichen Grüßen
>
> Rolf Brandt
>
>
>
>
--
pgadmin3 startet nicht in Netrunner OS (Arch Linux)
Mit freundlichen Grüßen
Rolf Brandt
the tabs in pgadmin3 (which remains very popular) aren't themed properly
> when wxGTK3 is used.
>
> See below screenshot; unstable is the wxGTK3 build.
>
> https://dev.solus-project.com/file/data/jzugkmqtn5ikapyg6p2o/PHID-FILE-
> 3gp2fiwycdzejhjcy3pq/pg-c.png
>
> Thank you!
>
>
Hello,
We are outphasing wxWidgets GTK2 build and we have been reported that
the tabs in pgadmin3 (which remains very popular) aren't themed properly
when wxGTK3 is used.
See below screenshot; unstable is the wxGTK3 build.
https://dev.solus-project.com/file/data/jzugkmqtn5ikapyg6p2o/PHID
46 matches
Mail list logo
