pgadmin4-server comming along for the ride

[richard coleman]

Installing pgadmin4 on a new kubuntu system.
install via:
sudo apt-get install pgadmin4-desktop
it automatically also installs pgadmin4-server.  If I try to remove
pgadmin4-server it also removes desktop.

How do I *just* install pgadmin4-desktop?

Thanks,
rik.

Re: Admin User Connect Privilege to Database

[richard coleman]

Josh,

This isn't really the list for it, but have you tried:

GRANT CONNECT ON DATABASE database_name TO public;

as the postgres superuser?

just a thought,
rik.



On Thu, Jun 29, 2023 at 3:41 PM Josh Klok  wrote:

> Hi,
>
> I'm relatively new to database management. I have a database setup
> currently with a few users. While configuring the user privileges within
> the database, I inadvertently removed the CONNECT privilege from all users
> (including the admin user).
>
> [image: image.png]
> Can you let me know how to re-enable the CONNECT privilege for all users?
>
> Thanks
>
> -Josh K
>

Re: pgAdmin 4 v7.2 Released

[richard coleman]

Also, just closing that dialog box now results in every saved connection
re-requesting the saved password all over again.

Why is this happening and how do I revert back to the previous behavior?

Thanks again,
rik.

On Thu, Jun 1, 2023 at 4:25 PM richard coleman 
wrote:

> Just upgraded to pgAdmin 4 version 7.2. Even though I have a
> config_local.py file with the string:
> MASTER_PASSWORD_REQUIRED=False
> I am still getting a "Migrate Saved Passwords" dialog upon start.
>
> How do I by pass this new dialog?
>
> Thanks,
> rik.
>
>
>>-
>>
>>
>>
>>

Re: pgAdmin 4 v7.2 Released

[richard coleman]

Just upgraded to pgAdmin 4 version 7.2. Even though I have a
config_local.py file with the string:
MASTER_PASSWORD_REQUIRED=False
I am still getting a "Migrate Saved Passwords" dialog upon start.

How do I by pass this new dialog?

Thanks,
rik.

On Thu, Jun 1, 2023 at 9:31 AM Akshay Joshi 
wrote:

> The pgAdmin Development Team is pleased to announce pgAdmin 4 version 7.2.
>
> This release of pgAdmin 4 includes 24 bug fixes and new features. For more
> details please see the release notes at:
>
> https://www.pgadmin.org/docs/pgadmin4/7.2/release_notes_7_2.html
>
> pgAdmin is the leading Open Source graphical management tool for
> PostgreSQL. For more information, please see:
>
> https://www.pgadmin.org/
>
> Note: From this release onwards pgAdmin 4 will now use the operating
> system's password store to save the server passwords in desktop mode
> instead of using Master Password.
>
> Notable changes in this release include:
>
> Features:
>
>-
>
>Add Option to only show active connections on Dashboard.
>-
>
>Allow pgAdmin to retrieve master password from external script/program.
>-
>
>Add an option to hide/show empty object collection nodes.
>-
>
>Added support to use standard OS secret store to save server/ssh
>tunnel passwords instead of master password in pgAdmin desktop mode.
>-
>
>Implement new PostgreSQL 15 features in publication dialog and SQL.
>
>
> Bugs/Housekeeping:
>
>-
>
>Fixed an issue where Foreign Key columns are shown in the wrong order
>in SQL and Properties.
>-
>
>Ensure that a new row should be added on top in the User Management
>dialog.
>-
>
>Fixed an issue where REVOKE ALL DDL in table SQL was added only for
>one role.
>-
>
>Tools menu should be toggled for "pause replay of wal" and "resume
>replay of wal".
>-
>
>Make the 'Connect to server' dialog a modal dialog.
>-
>
>Fixed an issue where PSQL tool prompts for password if using password
>exec command.
>-
>
>Fix circular reference error for the multirange data types in the
>query tool.
>-
>
>Fix an issue in the register server when setting the role, an
>arbitrary SQL query can be fired.
>-
>
>View SQL tab not quoting column comments.
>-
>
>VarChar Field Sizes are missing from Query's Grid header.
>
>
>
> Builds for Windows and macOS are available now, along with a Python Wheel,
>
> Docker Container, RPM, DEB Package, and source code tarball from:
>
> https://www.pgadmin.org/download/
>
> --
>
> Akshay Joshi
>
> pgAdmin Project
>
>

Re: error open app

[richard coleman]

Or if it's *very* large, a simple text (.txt) file.

rik.

On Fri, Nov 18, 2022 at 9:31 AM Ray O'Donnell  wrote:

> On 18/11/2022 10:48, Alina wrote:
> > Hello, when I open pgadmin4 app, I have this error message attached.
> > Please help me with this error.
>
> I'd be very wary about opening a Word file (or what claims to be a Word
> file) - you'd have a better chance of getting help by simply pasting the
> error message as plain text into your email.
>
> Ray.
>
> --
> Raymond O'Donnell // Galway // Ireland
> r...@rodonnell.ie
>
>
>
>

Re: PgAdmin ERD tool question

[richard coleman]

Aditya, Didier,

Agreed, a preference, or a couple of options, would probably make the most
sense.  I think the following options should cover most cases:

   - Limit to object dragged (current behavior)
   - Include immediate relationships ( 1 level )
   - Include x relationships ( user configurable )
   - Include all relationships ( may end up with the entire database, in
   hyper connected schema )

I hope that helps,
rik.

On Thu, Aug 18, 2022 at 1:28 AM Didier Gasser-Morlay 
wrote:

> May be limit the chain to one level, and revisit  the dependencies tree at
> each table dropped onto the ERD surface,
>
> On Thu, 18 Aug 2022 at 07:22, Aditya Toshniwal <
> aditya.toshni...@enterprisedb.com> wrote:
>
>> Hi Richard,
>>
>> The only problem I see with this is a table can refer to one or more
>> tables and the referred can refer to more tables and so on.
>> But I think that can be made optional with a preference setting.
>>
>> On Wed, Aug 17, 2022 at 9:18 PM richard coleman <
>> rcoleman.ascen...@gmail.com> wrote:
>>
>>> Aditya,
>>>
>>> How about an option to drag any/all related items when you drag one that
>>> is tied to other elements?
>>>
>>> Just a thought.
>>> rik.
>>>
>>> On Wed, Aug 17, 2022 at 5:33 AM Aditya Toshniwal <
>>> aditya.toshni...@enterprisedb.com> wrote:
>>>
>>>> Hi Didier,
>>>>
>>>> Since we can drop one table at a time, it is not possible to keep
>>>> relations without the referred table.
>>>> One possible solution could be to drag the referred table first and
>>>> then the referring table. But, this is not yet implemented. You can raise a
>>>> feature request here
>>>> https://redmine.postgresql.org/projects/pgadmin4/issues/new if you
>>>> think this solution will do.
>>>>
>>>>
>>>> On Wed, Aug 17, 2022 at 12:54 PM Didier Gasser-Morlay <
>>>> didie...@gmail.com> wrote:
>>>>
>>>>> Hello all,
>>>>>
>>>>> Using PGAdmin 4 v 6.12 in desktop mode, and I am starting to use the
>>>>> ERD tool and I have a question and a feature request (not too sure where 
>>>>> to
>>>>> put this one)
>>>>>
>>>>> Question :Drag and drop tables from browser tree to the diagram : PK
>>>>> are reverse engineered but FKs are left behind - How can I manage this? I
>>>>> was hoping that by using drap/drop of several tables the links would
>>>>> transfert over but I can't seem to multi select in the browser tree
>>>>>
>>>>>
>>>>> Feature request : I would love to be able to display only table name/
>>>>> Primary key field and any field involved in a fk. when just showing /
>>>>> explaining a database to a fellow worker showing just the relations &
>>>>> relationships goes a long way to quickly grasp the workings of a db. And 
>>>>> it
>>>>> also allows to have a compact view which printed serves as a reminder.
>>>>>
>>>>> Thanks for making and keeping PgAdmin the excellent product that it is
>>>>>
>>>>> Didier
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>> --
>>>> Thanks,
>>>> Aditya Toshniwal
>>>> pgAdmin Hacker | Software Architect | *edbpostgres.com*
>>>> <http://edbpostgres.com>
>>>> "Don't Complain about Heat, Plant a TREE"
>>>>
>>>
>>
>> --
>> Thanks,
>> Aditya Toshniwal
>> pgAdmin Hacker | Software Architect | *edbpostgres.com*
>> <http://edbpostgres.com>
>> "Don't Complain about Heat, Plant a TREE"
>>
>

Re: PgAdmin ERD tool question

[richard coleman]

Aditya,

How about an option to drag any/all related items when you drag one that is
tied to other elements?

Just a thought.
rik.

On Wed, Aug 17, 2022 at 5:33 AM Aditya Toshniwal <
aditya.toshni...@enterprisedb.com> wrote:

> Hi Didier,
>
> Since we can drop one table at a time, it is not possible to keep
> relations without the referred table.
> One possible solution could be to drag the referred table first and then
> the referring table. But, this is not yet implemented. You can raise a
> feature request here
> https://redmine.postgresql.org/projects/pgadmin4/issues/new if you think
> this solution will do.
>
>
> On Wed, Aug 17, 2022 at 12:54 PM Didier Gasser-Morlay 
> wrote:
>
>> Hello all,
>>
>> Using PGAdmin 4 v 6.12 in desktop mode, and I am starting to use the ERD
>> tool and I have a question and a feature request (not too sure where to put
>> this one)
>>
>> Question :Drag and drop tables from browser tree to the diagram : PK are
>> reverse engineered but FKs are left behind - How can I manage this? I was
>> hoping that by using drap/drop of several tables the links would transfert
>> over but I can't seem to multi select in the browser tree
>>
>>
>> Feature request : I would love to be able to display only table name/
>> Primary key field and any field involved in a fk. when just showing /
>> explaining a database to a fellow worker showing just the relations &
>> relationships goes a long way to quickly grasp the workings of a db. And it
>> also allows to have a compact view which printed serves as a reminder.
>>
>> Thanks for making and keeping PgAdmin the excellent product that it is
>>
>> Didier
>>
>>
>>
>>
>>
>
> --
> Thanks,
> Aditya Toshniwal
> pgAdmin Hacker | Software Architect | *edbpostgres.com*
> 
> "Don't Complain about Heat, Plant a TREE"
>

Re: Bulk CSV input within the GUI, not from file?

[richard coleman]

Jeong-hun Sin,

Have you tried just writing one or more INSERT statements in the query
tool?  In that way you won't need a CSV file and can just type them in the
text area as opposed to the data grid.

I hope that helps,

rik.

On Sat, Jun 11, 2022 at 7:18 PM Jeong-hun Sin  wrote:

> I wanted to input some 10 tuples into a simple table. I thought I could do
> that in a spreadsheet-like GUI as in MS SQL Management Studio, but the UI
> of PGAdmin was a lot more inconvenient. I looked around and found that it
> has an "import data" feature.  CSV was good-enough but it required the CSV
> to be a file. Can't pgAdmin have a textarea that allows users to type or
> paste CSV directly without using a file? I mean, creating a temporary CSV
> file and selecting the file in pgAdmin was not that convenient because
> pgAdmin's file browser dialogue is not as good as the OS native version.
>

Re: Question regarding Dashboard column resize

[richard coleman]

I've noticed it as well.  This greatly reduces the utility of the dashboard.

(pgAdmin4 v 6.9, Windows 10 Pro x64)

rik.

On Tue, May 31, 2022 at 11:51 AM Eric Katchan 
wrote:

> Hello, I have upgraded pgAdmin to v 6.9 and noticed that I was no longer
> able to resize columns in dashboard mode.  Have I missed something?  Is
> there a setting I could not find?
>
>
>
> Please advise
>
>
>
> Eric Katchan
>

pgAdmin 4 (v 6.9) still doesn't like to cancel background processes

[richard coleman]

Hi all,

Running pgAdmin4 version 6.9 on Windows 10 Pro x64.  It seems that pgAdmin
still doesn't like to stop processes.  I started a backup, then a couple of
seconds after it started I noticed a mistake and hit the "Stop Process"
button.  As of the time of this email it's been over 7,400 seconds and it's
still "Terminating the process..."

Is there any way to fix this, so that stop actually, I don't know,
terminates things?

[image: pg4_v6.9_unkillable_20220518_140620.png]

thanks,
rik.

(p.s. Shouldn't we drop the *4* in pgAdmin 4?  It seems rather silly to
refer to it as pgAdmin4, 6.9. )

Re: pgadmin4 for fedora 35

[richard coleman]

Dave,

Good to know,

thanks,
rik.


On Tue, Nov 9, 2021 at 8:43 AM Dave Page  wrote:

> Hi
>
> On Tue, Nov 9, 2021 at 12:41 PM richard coleman <
> rcoleman.ascen...@gmail.com> wrote:
>
>> Dave,
>>
>> Have you ever considered using something like flatpak (
>> https://flatpak.org/ ) for the Linux versions of pgAdmin?  It might;
>> make it easier to handle the many different distributions, and deal with
>> the different release schedules of the many dependencies that pgAdmin
>> relies upon.
>>
>
> Technologies like Flatpak make it significantly harder to maintain
> applications like pgAdmin, and for system administrators to ensure their
> systems are secure. This is primarily because they bundle third party
> libraries within the application package, which means that every time there
> is a security update to a library such as OpenSSL, we need to update the
> package we distribute, and the system administrator can't simply do a yum
> update or equivalent and be sure that their system is as secure as
> possible. It also means end users need to install a separate package
> management tool from the one that is native to their system.
>
> So, whilst (if we had the resources) I wouldn't object to supporting
> Flatpak and similar, I would certainly not want them to replace the
> standard native packages as the primary offering.
>
>
>>
>> Just a thought.
>>
>> rik.
>>
>>
>> On Tue, Nov 9, 2021 at 4:23 AM Dave Page 
>> wrote:
>>
>>>
>>>
>>> On Tue, Nov 9, 2021 at 8:11 AM toni incog  wrote:
>>>
>>>> fwiw That didn't work out. Symlinks where pointing to 3.9 though I
>>>> stopped at  Failed to exec Python script file
>>>> '/usr/pgadmin4/web/pgAdmin4.wsgi'... ModuleNotFoundError: No module
>>>> named 'flask'
>>>>
>>>
>>> :-(.
>>>
>>>
>>>> I guess I've to practice some patience.
>>>>
>>>
>>> Yeah, unfortunately. The issue is that one of the upstream libraries we
>>> use doesn't have a release that supports Python 3.10 yet. We have all the
>>> build system etc. setup and ready to go, but until they put out a new
>>> release we're kinda stuck.
>>>
>>>
>>>>
>>>> On Mon, 8 Nov 2021 at 10:01, toni incog  wrote:
>>>> >
>>>> > Ok, then I give that a try, thx!
>>>> >
>>>> > On Mon, 8 Nov 2021 at 09:56, Dave Page 
>>>> wrote:
>>>> > >
>>>> > >
>>>> > >
>>>> > > On Mon, Nov 8, 2021 at 8:34 AM Aditya Toshniwal <
>>>> aditya.toshni...@enterprisedb.com> wrote:
>>>> > >>
>>>> > >>
>>>> > >>
>>>> > >> On Mon, Nov 8, 2021 at 1:28 PM toni incog 
>>>> wrote:
>>>> > >>>
>>>> > >>> No easy way to fallback to python 3.9 in f35? 3.9 is installable
>>>> fwiw
>>>> > >>
>>>> > >> I'm not aware of any. @Dave do you have any ?
>>>> > >
>>>> > >
>>>> > > The F34 packages might work if you have 3.9 installed (I *think*
>>>> the symlinks in our venv should still point to the correct locations in
>>>> that case). There may be other things that don't work though.
>>>> > >
>>>> > >>>
>>>> > >>>
>>>> > >>> On Mon, 8 Nov 2021 at 06:17, Aditya Toshniwal
>>>> > >>>  wrote:
>>>> > >>> >
>>>> > >>> > Hi Toni,
>>>> > >>> >
>>>> > >>> > All of the python packages used by pgAdmin are not yet
>>>> available for 3.10. We're continuously testing pgAdmin on v3.10 to make it
>>>> work.
>>>> > >>> > Once pgAdmin works on v3.10, F35 builds can be made available.
>>>> > >>> >
>>>> > >>> > On Sat, Nov 6, 2021 at 6:35 PM toni incog 
>>>> wrote:
>>>> > >>> >>
>>>> > >>> >> No yum repos for f35 yet. Using the 34 repos has troubles with
>>>> f35
>>>> > >>> >> python3.10. Any fast solution for this? Is installing
>>>> python3.9 an
>>>> > >>> >> option. I'm not familiar with this pyhton world but became
>>>> dependend
>>>> > >>> >> on pgadmin4.
>>>> > >>> >>
>>>> > >>> >> thx
>>>> > >>> >>
>>>> > >>> >>
>>>> > >>> >
>>>> > >>> >
>>>> > >>> > --
>>>> > >>> > Thanks,
>>>> > >>> > Aditya Toshniwal
>>>> > >>> > pgAdmin Hacker | Software Architect | edbpostgres.com
>>>> > >>> > "Don't Complain about Heat, Plant a TREE"
>>>> > >>
>>>> > >>
>>>> > >>
>>>> > >> --
>>>> > >> Thanks,
>>>> > >> Aditya Toshniwal
>>>> > >> pgAdmin Hacker | Software Architect | edbpostgres.com
>>>> > >> "Don't Complain about Heat, Plant a TREE"
>>>> > >
>>>> > >
>>>> > >
>>>> > > --
>>>> > > Dave Page
>>>> > > VP, Chief Architect, Database Infrastructure
>>>> > > Blog: https://www.enterprisedb.com/dave-page
>>>> > > Twitter: @pgsnake
>>>> > >
>>>> > > EDB: https://www.enterprisedb.com
>>>>
>>>
>>>
>>> --
>>> Dave Page
>>> VP, Chief Architect, Database Infrastructure
>>> Blog: https://www.enterprisedb.com/dave-page
>>> Twitter: @pgsnake
>>>
>>> EDB: https://www.enterprisedb.com
>>>
>>
>
> --
> Dave Page
> VP, Chief Architect, Database Infrastructure
> Blog: https://www.enterprisedb.com/dave-page
> Twitter: @pgsnake
>
> EDB: https://www.enterprisedb.com
>

Re: pgadmin4 for fedora 35

[richard coleman]

Dave,

Have you ever considered using something like flatpak ( https://flatpak.org/
) for the Linux versions of pgAdmin?  It might; make it easier to handle
the many different distributions, and deal with the different release
schedules of the many dependencies that pgAdmin relies upon.

Just a thought.

rik.


On Tue, Nov 9, 2021 at 4:23 AM Dave Page  wrote:

>
>
> On Tue, Nov 9, 2021 at 8:11 AM toni incog  wrote:
>
>> fwiw That didn't work out. Symlinks where pointing to 3.9 though I
>> stopped at  Failed to exec Python script file
>> '/usr/pgadmin4/web/pgAdmin4.wsgi'... ModuleNotFoundError: No module
>> named 'flask'
>>
>
> :-(.
>
>
>> I guess I've to practice some patience.
>>
>
> Yeah, unfortunately. The issue is that one of the upstream libraries we
> use doesn't have a release that supports Python 3.10 yet. We have all the
> build system etc. setup and ready to go, but until they put out a new
> release we're kinda stuck.
>
>
>>
>> On Mon, 8 Nov 2021 at 10:01, toni incog  wrote:
>> >
>> > Ok, then I give that a try, thx!
>> >
>> > On Mon, 8 Nov 2021 at 09:56, Dave Page 
>> wrote:
>> > >
>> > >
>> > >
>> > > On Mon, Nov 8, 2021 at 8:34 AM Aditya Toshniwal <
>> aditya.toshni...@enterprisedb.com> wrote:
>> > >>
>> > >>
>> > >>
>> > >> On Mon, Nov 8, 2021 at 1:28 PM toni incog 
>> wrote:
>> > >>>
>> > >>> No easy way to fallback to python 3.9 in f35? 3.9 is installable
>> fwiw
>> > >>
>> > >> I'm not aware of any. @Dave do you have any ?
>> > >
>> > >
>> > > The F34 packages might work if you have 3.9 installed (I *think* the
>> symlinks in our venv should still point to the correct locations in that
>> case). There may be other things that don't work though.
>> > >
>> > >>>
>> > >>>
>> > >>> On Mon, 8 Nov 2021 at 06:17, Aditya Toshniwal
>> > >>>  wrote:
>> > >>> >
>> > >>> > Hi Toni,
>> > >>> >
>> > >>> > All of the python packages used by pgAdmin are not yet available
>> for 3.10. We're continuously testing pgAdmin on v3.10 to make it work.
>> > >>> > Once pgAdmin works on v3.10, F35 builds can be made available.
>> > >>> >
>> > >>> > On Sat, Nov 6, 2021 at 6:35 PM toni incog 
>> wrote:
>> > >>> >>
>> > >>> >> No yum repos for f35 yet. Using the 34 repos has troubles with
>> f35
>> > >>> >> python3.10. Any fast solution for this? Is installing python3.9
>> an
>> > >>> >> option. I'm not familiar with this pyhton world but became
>> dependend
>> > >>> >> on pgadmin4.
>> > >>> >>
>> > >>> >> thx
>> > >>> >>
>> > >>> >>
>> > >>> >
>> > >>> >
>> > >>> > --
>> > >>> > Thanks,
>> > >>> > Aditya Toshniwal
>> > >>> > pgAdmin Hacker | Software Architect | edbpostgres.com
>> > >>> > "Don't Complain about Heat, Plant a TREE"
>> > >>
>> > >>
>> > >>
>> > >> --
>> > >> Thanks,
>> > >> Aditya Toshniwal
>> > >> pgAdmin Hacker | Software Architect | edbpostgres.com
>> > >> "Don't Complain about Heat, Plant a TREE"
>> > >
>> > >
>> > >
>> > > --
>> > > Dave Page
>> > > VP, Chief Architect, Database Infrastructure
>> > > Blog: https://www.enterprisedb.com/dave-page
>> > > Twitter: @pgsnake
>> > >
>> > > EDB: https://www.enterprisedb.com
>>
>
>
> --
> Dave Page
> VP, Chief Architect, Database Infrastructure
> Blog: https://www.enterprisedb.com/dave-page
> Twitter: @pgsnake
>
> EDB: https://www.enterprisedb.com
>

Re: Running pgadmin4:5.5 behind reverse-proxy only shows progress indicator after successful login

[richard coleman]

Hi Jörg Liebig,

If it's the same issue that *still exists* when I connect over an RDP
session, I would try moving the window?  I find that the screen doesn't
refresh and it is actually all set behind that screen.  Moving the window
clears it up. That might not be *your* problem, but it won't hurt to try.

Good luck,

rik.

On Wed, Aug 11, 2021 at 12:05 PM Jörg Liebig  wrote:

> Hi,
>
> I'm trying to run pgadmin in a Kubernetes cluster with the following setup:
>+---+
>| Vouch |
>| Proxy |
>+-^---+-+
>  |   |
>  |   |
> +-++-+---v---+  +---+
> | Browser +> Reverse +--> /pgadmin4 |
> | || Proxy   |  |   |
> +-++-+  +---+
> pgadmin runs in a container at endpoint /pgadmin4 behind a reverse proxy
> using nginx (version 1.21.1). Proxy header X-Forwarded-* are set as follows:
> 1. X-Forwarded-For: $proxy_add_x_forwarded_for
> 2. X-Forwarded-Proto: https
> 3. X-Forwarded-Host: dev.<...>.com
> 4. X-Forwarded-Port: 443
> 5. X-Forwarded-Prefix: /pgadmin4
> 6. X-Script-Name: /pgadmin4
>
> Vouch Proxy (version 0.32.0) checks client credentials via a configured
> IDP.
>
> pgadmin itself is only configured with PGADMIN_DEFAULT_EMAIL and
> PGADMIN_DEFAULT_PASSWORD and runs using port 80, which is also used in
> nginx proxy configuration.
>
> After successful login I only see the progress indicator (see attachment).
> Looking at browser developer tools I see that besides 200 status responses
> there are a lot of 302 responses too, e.g., 302 GET dev.<...>.com
> /pgadmin4/browser
>
> Creating a port-forward in Kubernetes towards the /pgadmin4 container
> works right away.
>
> I tried to modify the pgadmin environment according to
> https://www.pgadmin.org/docs/pgadmin4/latest/container_deployment.html#pgadmin-x-forwarded-configuration
> by setting all values to "1". But it did not work. Furthermore, I don't
> understand the purpose and possible configuration setups.
>
> What can I do?
>
> Thanks in advance
> Jörg Liebig
>
>
>
>

Re: Resetting the pgadmin4 web user credentials

[richard coleman]

Kevin,
I don't think that the pgAdmin user and the database user are necessarily
the same thing (though I could be wrong) [see:
https://www.pgadmin.org/docs/pgadmin4/5.4/user_management.html ].  The
pg_hba.conf file defines what users/machines/methods are allowed to connect
to a postgresql server.  So for the first line in your example:

hostall all my.dbserver.ip.addr/32 trust

this would mean; *host * == connections made over TCP/IP, the first *all* ==
which databases, the second *all* == which users, the
*my.dbserver.ip.addr/32* == means *only* allow connections originating from
that *exact* ip address, and *trust* == allow connections without a
password or any other form of authentication [see:
https://www.postgresql.org/docs/13/auth-pg-hba-conf.html ].  I am guessing
that you have gotten the pgAdmin users confused with the postgresql
database users.

I would imagine that the pgAdmin server would need an entry in the
pg_hba.conf file for whatever machine pgAdmin is running on and I would be
amazed if it was using *trust* (or *no* authentication) to connect with.  I
use pgAdmin exclusively in desktop mode, so hopefully someone else who's
more familiar with server mode will chime in.

I hope that helps,

rik.




On Tue, Jul 27, 2021 at 6:28 PM Kevin Struckhoff 
wrote:

> Sorry re-posting with a corrected subject.
>
> Thanks. Kevin
>
>
> On Tuesday, July 27, 2021, 3:20:39 PM PDT, Kevin Struckhoff <
> kevinstruckh...@yahoo.com> wrote:
>
>
> After getting pgadmin4 installed and configured, I've found out that the
> user credentials I specified during the setup don't work very well. I've
> added the user to the postgres db using the adduser command. I updated the
> pg_hba.conf file with an entry just for the user but I get this error when
> trying to connect for the 1st time:
>
> FATAL: no pg_hba.conf entry for host " my.dbserver.ip.addr", user 
> "p...@p.com",
> database "postgres", SSL off
>
> psql postgres
> postgres-# adduser p...@p.com
> postgres-#\q
>
> pg_hba.conf entries (actual ip number hidden):
>
> hostall all my.dbserver.ip.addr/32 trust
> hostall p...@p.com my.dbserver.ip.addr /32 trust
> # for pgadmin4 web
>
> So I would have thought the 1st entry would cover all users. I can't
> create a linux user because the user name is invalid:
>
> useradd: invalid user name 'p...@p.com'
>
> So to make it work, I'd just like to set the username/password to the
> postgres user. Where can I do that? I don't see a .py or .conf file other
> than pg_hba.conf where the user is defined.
>
> Thanks. Kevin
>

Re: FK to partitioned table

[richard coleman]

Piotr,

Thanks for the question.  This is the pgAdmin4 (a GUI for managing
PostgreSQL databases) list.  You might have better luck on the postgres
list Pgsql-admin .

Good luck,

rik.

On Tue, Jun 29, 2021 at 8:28 AM Piotr Włodarczyk <
piotrwlodarczy...@gmail.com> wrote:

> Hello geeks,
>
> I have a question I can't find any answer.
>
> First we need some basic structure. So it is:
>
>
>   CREATE SCHEMA parts
>   AUTHORIZATION postgres;
>
>   DROP TABLE IF EXISTS parts.main;
>
>   CREATE TABLE IF NOT EXISTS parts.main
>   (
>   id bigserial NOT NULL,
>   id_ext bigint NOT NULL,
>   added timestamp without time zone,
>   CONSTRAINT pk PRIMARY KEY (id, id_ext)
>   ) PARTITION BY hash (id_ext);
>
>   ALTER TABLE parts.main
>   OWNER to postgres;
>
> Then we create a partitions:
>
>   CREATE TABLE IF NOT EXISTS parts.main_hash0 PARTITION OF parts.main FOR
> VALUES WITH (MODULUS 10, REMAINDER 0);
>   CREATE TABLE IF NOT EXISTS parts.main_hash1 PARTITION OF parts.main FOR
> VALUES WITH (MODULUS 10, REMAINDER 1);
>   CREATE TABLE IF NOT EXISTS parts.main_hash2 PARTITION OF parts.main FOR
> VALUES WITH (MODULUS 10, REMAINDER 2);
>   CREATE TABLE IF NOT EXISTS parts.main_hash3 PARTITION OF parts.main FOR
> VALUES WITH (MODULUS 10, REMAINDER 3);
>   CREATE TABLE IF NOT EXISTS parts.main_hash4 PARTITION OF parts.main FOR
> VALUES WITH (MODULUS 10, REMAINDER 4);
>   CREATE TABLE IF NOT EXISTS parts.main_hash5 PARTITION OF parts.main FOR
> VALUES WITH (MODULUS 10, REMAINDER 5);
>   CREATE TABLE IF NOT EXISTS parts.main_hash6 PARTITION OF parts.main FOR
> VALUES WITH (MODULUS 10, REMAINDER 6);
>   CREATE TABLE IF NOT EXISTS parts.main_hash7 PARTITION OF parts.main FOR
> VALUES WITH (MODULUS 10, REMAINDER 7);
>   CREATE TABLE IF NOT EXISTS parts.main_hash8 PARTITION OF parts.main FOR
> VALUES WITH (MODULUS 10, REMAINDER 8);
>   CREATE TABLE IF NOT EXISTS parts.main_hash9 PARTITION OF parts.main FOR
> VALUES WITH (MODULUS 10, REMAINDER 9);
>
> And finally one table connected by fk to parts.main:
>
>   -- Table: parts.main_additional
>
>   -- DROP TABLE parts.main_additional;
>
>   CREATE TABLE IF NOT EXISTS parts.main_additional
>   (
>   id bigserial,
>   id_main bigint NOT NULL,
>   id_ext bigint,
>   CONSTRAINT main_additional_pkey PRIMARY KEY (id),
>   CONSTRAINT fk_1 FOREIGN KEY (id_ext, id_main)
>  REFERENCES parts.main (id_ext, id) MATCH SIMPLE
>  ON UPDATE NO ACTION
>  ON DELETE NO ACTION
>   )
>
>   TABLESPACE pg_default;
>
>   ALTER TABLE parts.main_additional
>   OWNER to postgres;
>
>
> So we have partitioned table parts.main partitioned by hash of id_ext and
> having PK (id, id_ext).
>
> We have parts.main_addidtional table with some data related to parts.main.
> As you can see we have FK fk_1
>
>   (...)
>CONSTRAINT fk_1 FOREIGN KEY (id_ext, id_main)
>  REFERENCES parts.main (id_ext, id) MATCH SIMPLE
>  ON UPDATE NO ACTION
>  ON DELETE NO ACTION
>   (...)
>
> on parts.main_addidtional table. Because of parts.main is partitioned
> finnaly postgres create fk_1 as follows:
>
>   (...)
>   CONSTRAINT fk_1 FOREIGN KEY (id_ext, id_main)
> REFERENCES parts.main (id_ext, id) MATCH SIMPLE
> ON UPDATE NO ACTION
> ON DELETE NO ACTION,
> CONSTRAINT main_additional_id_ext_id_main_fkey FOREIGN KEY (id_ext,
> id_main)
> REFERENCES parts.main_hash0 (id_ext, id) MATCH SIMPLE
> ON UPDATE NO ACTION
> ON DELETE NO ACTION,
> CONSTRAINT main_additional_id_ext_id_main_fkey1 FOREIGN KEY (id_ext,
> id_main)
> REFERENCES parts.main_hash1 (id_ext, id) MATCH SIMPLE
> ON UPDATE NO ACTION
> ON DELETE NO ACTION,
> CONSTRAINT main_additional_id_ext_id_main_fkey2 FOREIGN KEY (id_ext,
> id_main)
> REFERENCES parts.main_hash2 (id_ext, id) MATCH SIMPLE
> ON UPDATE NO ACTION
> ON DELETE NO ACTION,
> CONSTRAINT main_additional_id_ext_id_main_fkey3 FOREIGN KEY (id_ext,
> id_main)
> REFERENCES parts.main_hash3 (id_ext, id) MATCH SIMPLE
> ON UPDATE NO ACTION
> ON DELETE NO ACTION,
> CONSTRAINT main_additional_id_ext_id_main_fkey4 FOREIGN KEY (id_ext,
> id_main)
> REFERENCES parts.main_hash4 (id_ext, id) MATCH SIMPLE
> ON UPDATE NO ACTION
> ON DELETE NO ACTION,
> CONSTRAINT main_additional_id_ext_id_main_fkey5 FOREIGN KEY (id_ext,
> id_main)
> REFERENCES parts.main_hash5 (id_ext, id) MATCH SIMPLE
> ON UPDATE NO ACTION
> ON DELETE NO ACTION,
> CONSTRAINT main_additional_id_ext_id_main_fkey6 FOREIGN KEY (id_ext,
> id_main)
> REFERENCES parts.main_hash6 (id_ext, id) MATCH SIMPLE
> ON UPDATE NO ACTION
> ON DELETE NO ACTION,
> CONSTRAINT main_additional_id_ext_id_main_fkey7 FOREIGN KEY (id_ext,
> id_main)
> REFERENCES parts.main_hash7 (id_ext, id) MATCH SIMPLE
> ON UPDATE NO ACTION
> ON DELETE NO ACTION,
> CONSTRAINT main_additional_id_ext_id_main_fkey

Re: pgAdmin 4 v5.4 Released

[richard coleman]

Akshay,

Thanks for pointing that out, I never realized that it was there ;)

rik.

On Fri, Jun 18, 2021 at 10:07 AM Akshay Joshi 
wrote:

> Hi Frank
>
> On Fri, 18 Jun, 2021, 2:42 pm Frank Limpert, 
> wrote:
>
>> At first: Thank you all for repairing Bug #6520 - CSV Export.
>>
>> 2.) Your idea to integrate *psql* into pgAdmin4 is interesting. Are
>> there any plans to integrate *pgcli* entirely? I have seen efforts on
>> this already documented in redmine.
>>
>> 3.) Opening the Query Tool (and other tools) in a new browser tab is
>> completely impossible in the *docker installation*. Even the
>> configuration option is gone. I would greatly appreciate having this
>> feature back.
>>
>
> The setting to opening the Query Tool( and other tools) in new browser
> tab is move to Browser -> Tab settings. Please check it.
>
>>
>> Happy computing...
>> Frank
>>
>> Am 17.06.21 um 12:21 schrieb Akshay Joshi:
>>
>> The pgAdmin Development Team is pleased to announce pgAdmin 4 version 5.4.
>>
>>
>>
>> This release of pgAdmin 4 includes 20 bug fixes and new features. For
>> more details please see the release notes at:
>>
>>
>>
>> https://www.pgadmin.org/docs/pgadmin4/5.4/release_notes_5_4.html.
>>
>>
>>
>> pgAdmin is the leading Open Source graphical management tool for
>> PostgreSQL. For more information, please see:
>>
>>
>>
>> https://www.pgadmin.org/
>>
>>
>>
>> Notable changes in this release include:
>>
>> Features:
>>
>>-
>>
>>PSQL Tool support (Beta)
>>
>>
>>
>> The PSQL tool allows users to connect to PostgreSQL or EDB Advanced
>> server using the psql command-line interface through their browser. Open
>> the PSQL tool from the Tools or browser tree context menu, or use the PSQL
>> tool button at the top of the browser tree. On the Windows platform, this
>> feature is available on Windows 10 (1809 version), and Windows Server 2019
>> and onwards.
>>
>>-
>>
>>Added support to browse binary path and set it for the different
>>database server version
>>
>>
>>
>> This feature allows the user to set the different binary paths for the
>> supported database server versions. Added browse button to select the
>> binary path along with validation button to validate the path. Validation
>> checks for the utilities and shows the version of the utilities.
>>
>>
>>
>>-
>>
>>Rotating the pgAdmin log files on the basis of size and age
>>
>>
>>
>> Using this feature the user will be able to set the log rotation on the
>> basis of size and age. Added configuration parameters LOG_ROTATION_SIZE and
>> LOG_ROTATION_AGE.
>>
>>
>>
>>-
>>
>>Window maximize/restore functionality for properties dialog
>>
>>
>>
>> This feature allows the user to maximize and restore the properties
>> dialog.
>>
>>
>>
>>-
>>
>>Support non-admin installation on Windows
>>
>>
>>
>>
>>
>> Bugs/Housekeeping:
>>
>>-
>>
>>Updated Flask-Security-Too to the latest v4.
>>-
>>
>>Added a mechanism to detect a corrupt/broken config database file.
>>-
>>
>>Fixed the issue of renaming the database by another user.
>>-
>>
>>Disable browser password saving in the runtime.
>>-
>>
>>Ensure that the Query Tool connection string should not be changed as
>>per the 'Query Tool tab title'.
>>-
>>
>>Fixed duplicate SQL issue for tables with more than one partition.
>>-
>>
>>Fixed an issue where the Foreground Color property of server dialog
>>does not work.
>>-
>>
>>Fixed an issue where a decimal number is appended for character
>>varying fields while downloading the data in CSV format.
>>
>>
>>
>> Builds for Windows and macOS are available now, along with a Python Wheel,
>>
>> Docker Container, RPM, DEB Package, and source code tarball from:
>>
>> https://www.pgadmin.org/download/
>>
>>
>>
>> --
>>
>> Akshay Joshi
>>
>> pgAdmin Project
>>
>>
>>

Re: pgAdmin 4 v5.4 Released

[richard coleman]

It looks like Bug #6520 has been squashed.  Thanks to the entire team for
their work in this and the other bug squashing/improvements. 👍
rik.

On Thu, Jun 17, 2021 at 6:21 AM Akshay Joshi 
wrote:

> The pgAdmin Development Team is pleased to announce pgAdmin 4 version 5.4.
>
>
>
> This release of pgAdmin 4 includes 20 bug fixes and new features. For
> more details please see the release notes at:
>
>
>
> https://www.pgadmin.org/docs/pgadmin4/5.4/release_notes_5_4.html.
>
>
>
> pgAdmin is the leading Open Source graphical management tool for
> PostgreSQL. For more information, please see:
>
>
>
> https://www.pgadmin.org/
>
>
>
> Notable changes in this release include:
>
> Features:
>
>-
>
>PSQL Tool support (Beta)
>
>
>
> The PSQL tool allows users to connect to PostgreSQL or EDB Advanced server
> using the psql command-line interface through their browser. Open the PSQL
> tool from the Tools or browser tree context menu, or use the PSQL tool
> button at the top of the browser tree. On the Windows platform, this
> feature is available on Windows 10 (1809 version), and Windows Server 2019
> and onwards.
>
>-
>
>Added support to browse binary path and set it for the different
>database server version
>
>
>
> This feature allows the user to set the different binary paths for the
> supported database server versions. Added browse button to select the
> binary path along with validation button to validate the path. Validation
> checks for the utilities and shows the version of the utilities.
>
>
>
>-
>
>Rotating the pgAdmin log files on the basis of size and age
>
>
>
> Using this feature the user will be able to set the log rotation on the
> basis of size and age. Added configuration parameters LOG_ROTATION_SIZE and
> LOG_ROTATION_AGE.
>
>
>
>-
>
>Window maximize/restore functionality for properties dialog
>
>
>
> This feature allows the user to maximize and restore the properties dialog.
>
>
>
>-
>
>Support non-admin installation on Windows
>
>
>
>
>
> Bugs/Housekeeping:
>
>-
>
>Updated Flask-Security-Too to the latest v4.
>-
>
>Added a mechanism to detect a corrupt/broken config database file.
>-
>
>Fixed the issue of renaming the database by another user.
>-
>
>Disable browser password saving in the runtime.
>-
>
>Ensure that the Query Tool connection string should not be changed as
>per the 'Query Tool tab title'.
>-
>
>Fixed duplicate SQL issue for tables with more than one partition.
>-
>
>Fixed an issue where the Foreground Color property of server dialog
>does not work.
>-
>
>Fixed an issue where a decimal number is appended for character
>varying fields while downloading the data in CSV format.
>
>
>
> Builds for Windows and macOS are available now, along with a Python Wheel,
>
> Docker Container, RPM, DEB Package, and source code tarball from:
>
> https://www.pgadmin.org/download/
>
>
>
> --
>
> Akshay Joshi
>
> pgAdmin Project
>

Re: Open pgAdmin in browser

[richard coleman]

Trung,

Yes, I can see how that would be annoying.  Hopefully the development team
can address these issues in future versions.

rik.

p.s. As for the last issue, you don't actually have to minimize the window,
just moving it a bit will refresh the display.  It isn't actually stuck, it
just looks like it.




On Thu, Jun 3, 2021 at 11:04 AM Trung Do  wrote:

> Thank you Richard and Rahul, I will try that.
>
> The reason I dislike the current standalone window is it has too many
> annoyances:
>
>  - When it was in a browser tab I can open multiple instances of
> pgAdmin in multiple tabs and switch between different servers very
> easily. Now I don't even think I can open multiple instances of the
> standalone app.
>  - If I accidentally close the app window now (which I do all the
> time), re-launching it takes 10 seconds instead of instantly like when
> it was a browser tab
>  - The standalone app doesn't remember the window size, it resets to
> default every time.
>  - Currently there is a bug where upon opening the app it would get
> stuck on the "Loading pgAdmin 4" screen until I minimize then
> un-minimize the app.
>
> Trung
>
> On Thu, 3 Jun 2021 at 10:55, Rahul Shirsat
>  wrote:
> >
> > Hi Trung,
> >
> > From pgAdmin4 v5.0 and above version, pgAdmin desktop will open in a
> browser-less standalone NWJS container.
> >
> > If you still want to use it in a browser, then you have to use it in a
> server mode. Refer -
> https://www.pgadmin.org/docs/pgadmin4/5.1/server_deployment.html for more
> details.
> >
> > On Thu, Jun 3, 2021, 8:10 PM Trung Do  wrote:
> >>
> >> Hi,
> >>
> >> Previously pgAdmin opened as a tab in my browser, which is great. Now
> >> it always opens in its own window. Is there a setting somewhere to get
> >> back the old behavior so that it opens in my browser again?
> >>
> >> Thanks,
> >>
> >> Trung
> >>
> >>
>
>
>

Re: Open pgAdmin in browser

[richard coleman]

Trung Do,

You know I think you are the *only* person I've heard from that actually
liked the old behaviour. ;)

I believe the only way is to either:

   - revert to an earlier version (not really recommended)
   - use pgAdmin4 in **server** mode as opposed to desktop mode

I hope that helps,

rik.

On Thu, Jun 3, 2021 at 10:40 AM Trung Do  wrote:

> Hi,
>
> Previously pgAdmin opened as a tab in my browser, which is great. Now
> it always opens in its own window. Is there a setting somewhere to get
> back the old behavior so that it opens in my browser again?
>
> Thanks,
>
> Trung
>
>
>

Re: Import fails on single quote.

[richard coleman]

Blake,

You might want to try escaping the single quotes in your data.  Either by
doubling them up or switching double quotes for dollar-quoted strings.

Just a thought,

rik.



On Tue, May 11, 2021 at 3:02 PM dsbw  wrote:

> Hello,
>
> Trying to import data, tab-delimited but unfortunately with quotes around
> string fields anyway. Like:
>
> 1234"JOHN""SMITH"5678
>
> PGAdmin import fails when the quoted value contains a single quote:
>
> 1234"EMPLOYEES'""CREDIT UNION"5678
>
> So the trailing quote (for possessive) after "EMPLOYEES" trips it up.
> Seems like, if one is inside a set of double-quotes, any single quotes
> should be ignored? (I know CSV is multiply and contradictorily defined, but
> still.)
>
> ===Blake===
>

Re: Rearrange Column

[richard coleman]

Dave,

Thanks, yes I got that, and the OP may indeed have wanted info on the
*reporting* results.  Since pgAdmin4 lets one administer/create/manipulate
the postgreSQL database/tables/views/etc. rearranging the underlying table
(much like Microsoft SQL Management Studio lets you do with a MS MQL
database table) was how *I* interpreted the question.

Since each table has a unique column structure, for pgAdmin4 to allow one
to specify a custom "SELECT * from Foo;" output would require it to have a
UI specific to each table for ordering and/or renaming each column, a menu
item to let the user run the custom select view and a place in a *pgAdmin4*
specific database to store all of this.  If there were any changes to the
table structure after that, it would have to check and inform the user or
risk throwing an error.  Seems like an awful lot of work.

If the OP wanted to have a custom view, wouldn't it make more sense to do
just that?  Create a custom postgreSQL view; "SELECT {fields in order and
optionally renamed as wanted} from Foo;"  Then all the user would need to
do is to use the bog standard pgAdmin4 "View/Edit Data" menu item to view
it in the preferred order anytime OP wanted to.

Just my $0.02.

rik.




On Thu, Apr 22, 2021 at 11:25 AM Dave Caughey  wrote:

> Rik,
>
> Clearly, if you do
>
> SELECT colA, colB FROM MyTable
>
> vs
>
> SELECT colB, colA FROM MyTable
>
> you'll get the results in a different sequence.  Obviously, using this
> approach has not manipulated the underlying table (your interpretation of
> what the OP is asking for), but perhaps the OP's question is that they're
> wondering if the *reporting* tool (i.e., pgAdmin) could hopefully allow you
> to rearrange the sequence in which a table's columns are displayed so that
> when you do a
>
> SELECT * FROM MyTable
>
> pgAdmin will take care of manipulating the results of the query to
> *display* the columns in a specified sequence.
>
> Yes, the OP currently has the ability to craft a custom query, e.g.,
>
> SELECT colA, colB, colZ, colT, colC, colQ, colD, colE...
>
> to get the exact order they want, but it would actually be nice if the
> reporting tool took care of this for you so you could just specify "SELECT
> *" and get the columns in the way you want to see them, or, should they be
> using "View/Edit Rows" pgAdmin would again show the rows in the prefered
> order.
>
> Cheers,
> Dave
>
>
> On Thu, Apr 22, 2021 at 11:01 AM richard coleman <
> rcoleman.ascen...@gmail.com> wrote:
>
>> Sachin,
>>
>> Umm, I hate to be the one to break it to you, but *postgreSQL *doesn't
>> support rearranging columns in a table, short of dropping them and
>> re-adding them in the desired order.  Since postgreSQL itself doesn't
>> support that, I would be truly amazed to learn that pgAdmin4 managed to
>> accomplish that trick.
>>
>> If I'm wrong, someone *please* let me know.
>>
>> rik.
>>
>> On Thu, Apr 22, 2021 at 9:53 AM Sachin Kumar 
>> wrote:
>>
>>> Hi Team,
>>>
>>> How can we rearrange the column of PostgreSQL using PGADMIN?
>>>
>>> --
>>>
>>> Best Regards,
>>> Sachin Kumar
>>>
>>

Re: Rearrange Column

[richard coleman]

Sachin,

Umm, I hate to be the one to break it to you, but *postgreSQL *doesn't
support rearranging columns in a table, short of dropping them and
re-adding them in the desired order.  Since postgreSQL itself doesn't
support that, I would be truly amazed to learn that pgAdmin4 managed to
accomplish that trick.

If I'm wrong, someone *please* let me know.

rik.

On Thu, Apr 22, 2021 at 9:53 AM Sachin Kumar 
wrote:

> Hi Team,
>
> How can we rearrange the column of PostgreSQL using PGADMIN?
>
> --
>
> Best Regards,
> Sachin Kumar
>

Re: PGAdmin 4 V5 scroll-bars

[richard coleman]

Darren,

I think I understand what you are trying to get at with your post, but I am
afraid it comes across as a bit insensitive.  Trackpad/touch control
surfaces are very difficult for me, and I would imagine like situated
people, to utilize.  Suggesting that they try a "...*more modern (but still
almost *[sic] *decade old)*..." interface is like suggesting a blind person
stop using a braille interface for a color monitor.  How did you put it?

> "*The difference is almost as night and day as knowing how to touch type
> vs hunt and peck.*"


You might want to try and understand that not everyone is as abled as
yourself.

Thanks,

rik.

On Tue, Mar 23, 2021 at 2:08 PM Darren Duncan 
wrote:

> On 2021-03-23 1:52 a.m., H. v. Loewenfeld, Philipp wrote:
> > -Original Message-
> >> That's weird, I usually consider scroll wheels an order of magnitude
> more
> >> handy than clicking the scroll arrow buttons.
> >
> > The mouse wheel only works in one dimension. And you can't directly jump
> to a
> > position (e.g. "at the end" or "75% down") like you can with the scroll
> bars.
>
> The more modern (but still almost decade old) ones that are touch/trackpad
> based
> work in both dimensions, such as the Apple Magic Mouse, or otherwise any
> trackpad/touch control surface.  And with a standard inertia feature going
> to
> the end is often a quick flick of the finger, or the keyboard End key.
>
> I don't disagree that broken scroll bar UI is a bad thing and should be
> priority
> fixed.
>
> But I recommend that people will have a more pleasant experience in
> computing
> generally if they try other common input device alternatives.  The
> difference is
> almost as night and day as knowing how to touch type vs hunt and peck.
>
> -- Darren Duncan
>
>
>

Re: PGAdmin 4 V5 scroll-bars

[richard coleman]

Darren,

Same issue here.  Windows 10 Enterprise, pgAdmin 4 v5 desktop mode.  Scroll
bar visible but useless.  As you can see from the original poster's screen
shot, the problem with text overwriting the scroll bars hasn't been
addressed either.

As for using a scroll wheel, not all of us have one.  I *need* to use a
trackball which doesn't have a scroll wheel.  My only option currently is
to click inside the query editor text area and use the arrow keys on the
keyboard.  Very painful when your query is a couple of hundred lines (or
more) long.

Ideally:

   - the text should stop overwriting the scroll bar areas
   - the scroll bars should be functional
   - the up and down arrow buttons would be returned to the top and bottom
   of the scroll bars respectively
   - a minimum size would be set for the scroll bars.  Currently they try
   to be proportional and as the size of the query increases at some point
   they become too tiny to be useful.

Thanks,

rik.

On Tue, Mar 23, 2021 at 12:33 AM Darren Duncan 
wrote:

> That's weird, I usually consider scroll wheels an order of magnitude more
> handy
> than clicking the scroll arrow buttons.  One reason is that its a very
> large
> target, the arrow simply has to be anywhere within the window to be
> scrolled,
> and not by the tiny arrows.  Another reason, a big one, is that the scroll
> wheel
> lets you scroll windows without bringing them into focus, such as if they
> are
> partly behind something else, where clicking the arrows brings that window
> in to
> focus. -- Darren Duncan
>
> On 2021-03-22 9:29 p.m., Don wrote:
> > Yes, that does work. It's just not as handy...
> >
> > -- Original Message --
> > From: "Darren Duncan" 
> > To: pgadmin-support@lists.postgresql.org
> > Sent: 23/03/2021 3:01:27 PM
> > Subject: Re: PGAdmin 4 V5 scroll-bars
> >
> >> What about the scroll wheel?  Can you scroll the windows without
> directly
> >> touching the scroll bars like in other applications? -- Darren Duncan
> >>
> >> On 2021-03-22 5:10 p.m., Don wrote:
> >>> The PGAdmin 4 V5 Query tool vertical and horizontal scroll-bars don't
> work.
> >>> They are visible as per the screen-shot but the mouse pointer doesn't
> appear
> >>> when floating over the editor scroll-bars.
> >>>
> >>> This happens when right-clicking on an object and selecting Query tool
> and
> >>> either entering some long SQL statements or pasting a query from
> another
> >>> script.  It also happens when a function is right-clicked and
> Scripts>Create
> >>> Script is selected.  Resizing the window does not make a difference.
> >>>
> >>> The scroll-bars do work on the left hand pane where the function list
> is.
> >>>
> >>> I'm using it in desktop mode in a Windows 10 64-bit environment.
> >>>
> >>> Please look into this issue and let me know if more information is
> required.
> >>
> >>
> >
> >
>
>
>
>

Re: pgAdmin desktop app fatal error

[richard coleman]

Alex,

It sounds like you might have a pgAdmin4 *pre-verson 5 *installation on
your machine.  Version 5 is the one that doesn't rely on an external
browser, previous versions did.  Adding to the confusion is that when
pgAdmin 4 v5 is installed, it *doesn't remove* any pre-version 5
installations.  This has led me to the unfortunate experience of selecting
pgAdmin 4 in windows and sometimes getting version 4 and other times
version 5.  I solved the issue for myself by *uninstalling* version 4.

Good luck, I hope this helps,

rik.

On Fri, Mar 12, 2021 at 2:12 PM Alex Creznic  wrote:

> Sir/Ma'am,
>
> When I attempted to open pgAdmin 4 on my Windows 10 operating system which
> has SQL version 13 installed, I received a fatal error. Now, everytime that
> I try to run pgAdmin 4, it uses Microsoft's Edge browser to work, bypassing
> the native desktop application. How do I fix this issue? I would like to
> use the desktop application if possible. I appreciate your time and look
> forward to your answer.
>
> Alex Creznic
>

Re: Switch PG Versions

[richard coleman]

Edson,

Of course not.  What you can do is install multiple versions of postgreSQL
in parallel (I've done it on Windows and Ubuntu Server).  It's why they are
each put into their own version numbered  directory.  For example, a
Windows machine running versions 10, 12, and 13 would have a default file
structure like this;

C:\Program Files\PostgreSQL\10\... (various folders including data, where
your database data resides)
C:\Program Files\PostgreSQL\12\... (various folders including data, where
your database data resides)
C:\Program Files\PostgreSQL\13\... (various folders including data, where
your database data resides)

As you can see, as long as the data folders for each postgreSQL version are
kept in different locations and you are running postgreSQL on different
ports, you can run as many copies of postgreSQL in parallel as you have
resources (hard drive space, memory, CPU, etc.).  Things only get tricky
when you want to run multiple instances of the *same* version of postgreSQL
on the same machine for some reason.  In this case you would have to
deviate from the default folder structure.  If you wanted to run three
copies of postgreSQL 13 on the same machine in parallel then something like
this would do;

C:\Program Files\PostgreSQL\13\... (various folders including data, where
your database data resides)
C:\Program Files\PostgreSQL\13a\... (various folders including data, where
your database data resides)
C:\Program Files\PostgreSQL\13b\... (various folders including data, where
your database data resides)

Of course, you would need to go back through your configuration files to
make sure they matched your alternative layout.  You would also still need
to be running them on different ports.

I hope that helps,

rik.


On Thu, Mar 4, 2021 at 4:03 PM Edson Richter 
wrote:

> Yes it’s possible to do as Richard noticed. But you cannot share at any
> chance the data folder!
>
> This will corrupt your data making irrecoverable.
>
> Even not having two versions online, you cannot shutdown version 10 and
> startup version 12 (or any combination of major versions) on same data
> folder – this will lead to data loss.
>
>
>
> Regards,
>
>
>
> Edson
>
>
>
> Enviado do Email  para
> Windows 10
>
>
> --
> *De:* Richard Brockie 
> *Enviado:* Thursday, March 4, 2021 5:49:05 PM
> *Para:* pgadmin-support lists.postgresql.org <
> pgadmin-support@lists.postgresql.org>
> *Assunto:* Re: Switch PG Versions
>
> Hi Jack,
>
> I was in a similar situation with an old application using pg v9. I
> installed different versions of postgres with homebrew on Catalina. I
> currently have versions 9, 11 & 12 installed and can have them all running
> in parallel listening on different ports. I connect to them all from a
> single instance of pgAdmin4 over their respective ports. Testing the
> application with the new pg version is also just a port change in the
> configuration. It works very well.
>
> Best wishes,
> R.
>
>
> On Thu, Mar 4, 2021 at 11:52 AM Jack Royal-Gordon 
> wrote:
>
> I’m using the EDB PG installation on Mac OS 11.1 (Big Sur), which seems to
> offer multiple versions. I’m currently running PG10, but I’m looking to
> upgrade to PG13 and would like to test with it first. Can I (and if so then
> how do i) switch back and forth between PG versions?
>
>
>
> --
> R.
>
> Richard Brockie
>
> Real-time bicycle race management - www.ontheday.net
>

Re: How do I remove this stupid "master password"?

[richard coleman]

[ HOW TO DISABLE MASTER PASSWORD feature in pgAdmin4 ]

Vladimir,

I sympathize with you.  I have had some extensive discussions with the head
developer, unfortunately it doesn't seem to be something that he is willing
to address.  It's built to address a *remote* threat vector, one that the
vast majority of users would not be susceptible to, nor would they agree
that the minimal additional security provided warrants the lost time and
inconvenience that having it entails.  Since he believes so strongly in
this, it is set to a default of being on and not only is the setting *not*
exposed in the configuration UI, but it makes use of a non-existent file in
a location that typically only administrators have access to.  Since many
(most) users who will be using this in desktop mode already have these
permissions, all it does is force them to either; use a stupidly simple
master password (a single space is sufficient), or research the
byzantine instructions to create a config_local.py file with the magic
line; "MASTER_PASSWORD_REQUIRED=False" .  It doesn't help that the official
documentation located here
https://www.pgadmin.org/docs/pgadmin4/5.0/config_py.html, gives a location
for config_system.py.  It usually doesn't exist and more importantly is
**not** the location where the config.py, config_distro.py, or the all
important config_local.py (that you need to create to disable the MASTER
PASSWORD feature) resides.  Of course, upgrading from pgAdmin4 4.x to
pgAdmin4 5.0 re-enables the MASTER PASSWORD feature (⋋▂⋌).

So, until the devs either; add the option to control the MASTER PASSWORD
feature into the config UI where it belongs, or change things, here are the
steps to disable it.

   1. Make sure pgAdmin4 is not running (if you are using pre-version 5,
   make sure it isn't running in the tray)
   2. Locate the pgadmin4 *config.py* file (it will be in a *web*
   sub-directory parallel to the directory containing the executable)
   3. Create a file named *config_local.py* in the same directory as the
   config.py file (you will probably need admin or equivalent permissions)
   4. Enter the line: MASTER_PASSWORD_REQUIRED=False into that file and save
   5. Start pgAdmin4 and enjoy your MASTER PASSWORD free life

I hope that helps anyone else still struggling with this.

rik.

On Sun, Feb 28, 2021 at 5:47 AM Vladimir Nicolici  wrote:

> Apparently, some parts of the message were lost when posting it through
> postgresql-archive.org, so I attached a PDF version of my previous
> message which includes the missing sections. Sorry about that.
>
>
>
> Sent from Mail  for
> Windows 10
>

Re: query tool csv/txt output file extension choice and encoding

[richard coleman]

Dave,

I concur with Alain.

On Fri, Feb 5, 2021 at 3:22 PM Dave Caughey  wrote:

> Always naming the file as ".csv", regardless of the delimited used, was a
> bug that was fixed.
>
> In my case it was a bug that was created.


> The problem with always naming a file as ".csv" is that Excel then blindly
> assumes that the file actually does contain comma-delimited fields, and
> bypasses the Import From Text Wizard, so if you use anything other than
> commas (e.g., you want TAB separators), then Excel won't split your file
> into multiple columns correctly.   Therefore, before the bug was fixed, you
> had to manually rename all of pgAdmin's "export to file" outputs to
> ".txt".  (Exactly what you don't want to have to do, too!)
>
> No, both Alain and myself *now* have to rename the .txt files to .csv
files.  In my case it's because LibreOffice won't open it in Calc with a
txt extension, but instead try to open it in Write.  If I leave it .txt I
have to; manually start Calc, then select the file, then try to import it.
If it's named .csv a simple double-click opens the file in Calc and in the
CSV import wizard that correctly handles files delimited by comma, tab, ~,
|, ;, or anything else you like.


> Note, if your file is ends with ".txt", then simply doing a "File" |
> "Open" in Excel will automatically/correctly invoke the Import from Text
> Wizard, and let you pick the delimiter you want (and it does a good job of
> auto-detecting).  Easy!
>
> And, if you don't want to use commas as your delimiter (for any number of
> reasons), then you can change that in pgAdmin by going to "File" |
> "Preferences" | "CVS/TXT Output" and choose your preferred delimiter (e.g.,
> Tab, "|", etc.), and thereafter that's what pgAdmin will always use when
> you do an "export to file", but will give it an ".txt" extension so Excel
> won't screw up opening the file because it's expecting commas as delimiters.
>
> Currently the *only* options pgAdmin4 gives me are; semicolon, comma,
vertical bar, or tab.  I can apparently just type whatever I want, but
that's hardly obvious.  And comma is a very bad choice for European
countries where sixteen hundred point fifty-two would be written as 1600,52
as opposed to 1600.52 on this side of the pond.  You might be suffering
from just a touch of Americentric bias.


> Cheers,
> Dave
>
>
> On Fri, Feb 5, 2021 at 1:25 PM Alain Dupeyron  wrote:
> >
> > Hi,
> >
> > I'm using frequently the download file function in the query tool. In
> previous version of PgAdmin4, I select field separator ";"  and file was
> always generated with extension .csv and can be opened directly by Excel in
> one click with correct columns !
> >
> > Now I have always .txt extension (since 4.28 or before, I'm in PgAdmin
> 4.29 for now) but the .txt file do not open directly in excel
> > I Have to launch excel and open it but colums are not detected in my
> French excel, I have to convert data...(idem with TAB
> separator)...fastidious !
> > Or I have to save the file from the browser, then navigate to file, then
> I change its extension to .csv, confirm and then the file is opened
> correctly...fastidious !
> >
> > When I choose field separator "," in PgAdmin, then file is generated
> with extension .csv but colums are not detected in French Excel (comma is
> the decimal number separator in France...)
> >
> > => How can I "force" or choose in Pgadmin to always generate file with
> extension .csv independently of selected field separator ?
> >
> >
> > 2nd point: Can we choose file encoding of generated file too ? it's in
> UTF-8 now (was plateform dependant in PgAdmin 3?)
> > accentuated characters are not detected corretly by french excel
> (expecting by default my Windows-1252 plateform encoding), I have to import
> file in excel and to select the right utf8 encoding in a huge encoding
> list...
> >
> > Other approach : copy from query result then paste in excel and save the
> file myself...
> > accent are ok but column header are missing, I need to select the option
> on each new query tab "copy with header" => there is no pgAdmin preferences
> for that point ? (was in PgAdmin 3)
> >
> >
> > Yes we can blame Excel/Windows and csv format but it's the only download
> format proposed here  for spreadsheet tool and only theses 2-3
> configurations are missing to parametrize it as expected by end user
> platform...
> >
> > Thanks
>

Re: Testing required: pgAdmin 4 with new desktop runtime

[richard coleman]

Dave,

Sounds promising, can the new beta be installed alongside the existing
version?

Thanks,

rik.

On Thu, Jan 21, 2021 at 10:56 AM Dave Page  wrote:

> All,
>
> As you know, when run in Desktop mode, pgAdmin 4 uses a server process
> which runs all the time and opens a browser window to display the UI. Very
> early versions used a Qt based runtime that integrated the browser and
> server which gave a much more "normal" application feel, but unfortunately
> we found that the Qt browser components had performance issues.
>
> We've been working on a new runtime (based on NWjs, similar to Electron)
> to allow us to get rid of the separate server process, and I'm please to
> offer builds for testing at:
>
> https://developer.pgadmin.org/builds/nwjs-2021-01-21-1/
>
> There you'll find an installer for 64 bit Windows, a DMG for macOS, and
> RPM and DEB packages for Fedora 31, 32 & 33, RHEL/CentOS 7 & 8, Debian 9,
> 10 & 11 and Ubuntu 18.04, 20.04 and 20.10.
>
> These builds are based on development code currently in git that will be
> released as v4.30 next week. This includes phase 1 of our Kerberos support
> (for logging into pgAdmin, but *not* the database servers), and the new ERD
> tool. This code is still going through QA and final improvement, so please
> bear that in mind.
>
> We're aiming to release v5.0 of pgAdmin 4 in late February, based on the
> new runtime, so would appreciate as much help and feedback as we can get
> prior to the release.
>
> Whilst I'm writing, I'd also like to give an update on platform support
> changes;
>
> - As previously noted in release announcements, Windows 32 bit builds are
> deprecated. v4.29 will be the last 32 bit Windows build supported.
>
> - Canonical have dropped support for Ubuntu 19.10, and now removed all of
> the packages repositories. We have therefore had to drop support for it as
> well; the last supported version of pgAdmin on Ubuntu 19.10 will be v4.29.
>
> - Due to the age of the Python version it ships with, we've had to stop
> producing builds for Ubuntu 16.04 (some of the security related Python
> modules are no longer supported on older Python versions). v4.30 will be
> the last version supported on Ubuntu 16.04.
>
> - Builds for Ubuntu 20.10 and Debian 11 (Bullseye/testing) have been added
> for the v4.30 release onwards.
>
> Thank you!
>
> --
> Dave Page
> Blog: http://pgsnake.blogspot.com
> Twitter: @pgsnake
>
> EDB: http://www.enterprisedb.com
>
>

Re: Varying Character comparison

[richard coleman]

Joseph,

This is really an SQL question, not something specific to PostgreSQL or
pgAdmin.  That being said, it looks like your e.index_entry field is of
type varchar (character varying) and you are trying to compare it to an
int.  If that is the case you will need to either cast the e.index_entry
field in your queries to INT (which will fail if any aren't castable to
that type, or wrap your 2111300 in quotes (ex:'2111300' ) to make it a
string as opposed to an int.

I hope that helps,

rik.



On Wed, Jan 6, 2021 at 1:25 PM Joseph Ruffino 
wrote:

> Hi,
>
>
>
> I am not sure if this is how I add a question, but I cannot find anything
> on lists.postgesql.org.
>
>
>
> I am having a problem with a SQL that I am running in pgAdmin 4.27.  The
> SQL is being used to check for duplicates in our PostgreSQL DB.
>
>
>
> I am trying to edit out the barcode (*e.index_entry*) when it is equal to
> *2111300*.  When I run it with the above, I get and error:
>
> ERROR: operator does not exist: character varying <> integer
>
> LINE 66: and e.index_entry != 2111300 ^
>
> HINT: No operator matches the given name and argument type(s). You might
> need to add explicit type casts.
>
>
>
> I have tried *<>* and adding single quotes around 2111300. The <> gets
> the same error, and the single quotes ‘’ has it run for a long time.
>
>
>
> Any help would be appreciated.
>
>
>
> Here is the SQL we are using with the lines I use highlighted:
>
>
>
> SELECT
>
> r.creation_date_gmt as created,
>
> e.index_entry as barcode,
>
> 'p' || r.record_num || 'a' as patron_record_num,
>
> pn.last_name || ', ' ||pn.first_name || COALESCE(' ' ||
> NULLIF(pn.middle_name, ''), '') || ' ' || pr.birth_date_gmt as patron,
>
> pr.ptype_code,
>
> pr.activity_gmt,
>
> pr.expiration_date_gmt,
>
> pr.mblock_code as block_code,
>
> pr.owed_amt::float8::numeric::money as owed_amt,
>
> pr.home_library_code
>
> -- pr.home_library_code,
>
>
>
> FROM
>
> sierra_view.patron_record_fullname as pn
>
>
>
> JOIN
>
> sierra_view.patron_record as pr
>
> ON
>
> pr.record_id = pn.patron_record_id
>
>
>
> JOIN
>
> sierra_view.record_metadata as r
>
> ON
>
> r.id = pr.record_id
>
>
>
> JOIN
>
> sierra_view.phrase_entry AS e
>
> ON
>
> (e.record_id = r.id) AND (e.index_tag = 'b') AND
> (e.varfield_type_code = 'b')
>
>
>
> WHERE
>
> pr.birth_date_gmt || pn.first_name || COALESCE(' ' ||
> NULLIF(pn.middle_name, ''), '') || ' ' || pn.last_name
>
> IN
>
> (
>
> SELECT
>
>
>
> p.birth_date_gmt ||
>
> n.first_name || COALESCE(' ' ||
> NULLIF(n.middle_name, ''), '') || ' ' || n.last_name as patron_name
>
> -- e.index_entry,
>
> -- count(*) as matches
>
>
>
> FROM
>
> sierra_view.record_metadata AS r
>
>
>
> JOIN
>
> sierra_view.patron_record AS p
>
> ON
>
> p.record_id = r.id
>
>
>
> JOIN
>
> sierra_view.patron_record_fullname AS n
>
> ON
>
> n.patron_record_id = r.id
>
>
>
> -- JOIN
>
> -- sierra_view.phrase_entry AS e
>
> -- ON
>
> --   (e.record_id = r.id) AND (e.index_tag = 'b') AND
> (e.varfield_type_code = 'b')
>
>
>
> WHERE
>
> r.record_type_code = 'p'
>
> -- and r.creation_date_gmt >= '2017-05-01'
>
>
>
> and p.mblock_code != 'd'
>
> and e.index_entry  != 2111300
>
>
>
> GROUP BY
>
> p.birth_date_gmt,
>
> patron_name,
>
> p.ptype_code
>
> -- e.index_entry
>
>
>
> HAVING
>
> COUNT(*) > 1
>
> )
>
>
>
> -- and pr.mblock_code != 'd'
>
>
>
> ORDER BY
>
> pn.last_name || pn.first_name || pr.birth_date_gmt || COALESCE(' ' ||
> NULLIF(pn.middle_name, ''), ''),
>
> pr.ptype_code ASC,
>
> pr.activity_gmt DESC
>
>
>
> Joseph A. Ruffino
>
> Gail Borden Public Library District
>
> Web Programmer
>
> 270 N. Grove Ave.
>
> Elgin, IL 60120
>
> Phone: (847) 429-5986 Fax: (847) 608-5201
>
> http://www.gailborden.info
>
>
> PLEASE NOTE: Pursuant to Illinois State Law, e-mail communication to and
> from this address may be subject to public disclosure.
>

Re: Extra Paranthesis on joins on saving a view

[richard coleman]

Alex,

Sounds like you would like to register some *feature requests* for
pgAdmin4.  Your best bet would be to enter them here:

https://redmine.postgresql.org/projects/pgadmin4

One item per feature request.

Good luck,

rik.

On Wed, Dec 2, 2020 at 8:44 PM Alex Williams 
wrote:

> Hi,
>
> I'm not sure if this is something new but in previous versions of pgadmin
> (currently using 4.27 where this is happening,) when creating a view, more
> or less, my original sql was maintained, but now it's mangling the joins
> like MS Access does with the Jet database with lots of parenthesis's (yes,
> I still use Access 2000.) Is there a way to disable this? I find it very
> difficult to parse and wind up removing them all only to have come back
> when saved when I'm done modifying / saving the view.
>
> Also, can you:
> 1. Allow renaming tables/functions/etc... without having to invoke
> propertiesit's very slow sometimes to bring up that dialogand
> sometimes I use rename just to copy a object name, not to rename it.
>
> 2. When running View/Edit->First 100 Rows, can you not lock it, i.e., it's
> a convenient way to have the select statement written without typing and
> then you add the predicates/joins.
>
> 3. When creating a table, can you please allow rearranging of the columns.
>
> Thanks,
>
> Alex
>
>
>
>

Re: PGAdmin4 v4.28 Windows Chrome

[richard coleman]

Marcelo,

This is a known issue with the latest version under windows.  The solution
is documented here:

https://www.pgadmin.org/faq/#12


TLDR;
To resolve the issue, use the Registry Editor and reset the value of
HKEY_CLASSES_ROOT\.js\Content Type to:

text/javascript

Good luck,

rik.

On Fri, Nov 27, 2020 at 6:50 AM Marcelo (Hotmail) 
wrote:

> Hello PGAdmin Team!
>
> I downloaded the latest version of PGAdmin, and when I execute the app,
> I´m receiving this error:
>
> (index):1 Refused to execute script from '
> http://127.0.0.1:59723/static/vendor/require/require.min.js?ver=42800'
> because its MIME type ('text/plain') is not executable, and strict MIME
> type checking is enabled.
> (index):39 Uncaught ReferenceError: require is not defined
> at (index):39
> (anonymous) @ (index):39
> (index):1 Refused to execute script from '
> http://127.0.0.1:59723/static/js/generated/vendor.main.js?ver=42800'
> because its MIME type ('text/plain') is not executable, and strict MIME
> type checking is enabled.
> (index):1 Refused to execute script from '
> http://127.0.0.1:59723/static/js/generated/vendor.others.js?ver=42800'
> because its MIME type ('text/plain') is not executable, and strict MIME
> type checking is enabled.
> (index):1 Refused to execute script from '
> http://127.0.0.1:59723/static/js/generated/pgadmin_commons.js?ver=42800'
> because its MIME type ('text/plain') is not executable, and strict MIME
> type checking is enabled.
> (index):128 ReferenceError: require is not defined
> at (index):118
> (index):136 Uncaught ReferenceError: require is not defined
> at (index):136
> (anonymous) @ (index):136
> More info
>
> Windows 10 Pro 64 bits
> Chrome 87.0.4280.66
> PG Admin 4.28
>
> ---
> []´s
> Best regards and take care
> Marcelo
>

Re: pg Admin 4 v4.28 Errors on launch

[richard coleman]

tito,

This is a known issue with the latest version under windows.  The solution
is documented here:

https://www.pgadmin.org/faq/#12


TLDR;
To resolve the issue, use the Registry Editor and reset the value of
HKEY_CLASSES_ROOT\.js\Content Type to:

text/javascript


Good luck,

rik.

On Thu, Nov 12, 2020 at 1:35 PM tito.calleros 
wrote:

> I have the same problem, I just upgrade from v4.27 to v4.28.
>
> Refused to execute script from
> 'http://127.0.0.1:57313/static/vendor/require/require.min.js?ver=42800'
> because its MIME type ('text/plain') is not executable, and strict MIME
> type
> checking is enabled.
>
> (index):39 Uncaught ReferenceError: require is not defined at (index):39
>
>
>
> --
> Sent from:
> https://www.postgresql-archive.org/PostgreSQL-pgadmin-support-f2191615.html
>
>
>

Re: Start pgadmin4 server

[richard coleman]

mrivera,

Welcome.  Running pgAdmin4 doesn't require you to be running, nor start
running a local postgreSQL server.  There may be some confusion in that
pgAdmin *itself* is a server (just not a postgreSQL server).  Actually
pgAdmin4 is just the back end, it relies on a browser to provide a user
interface (UI).  It can be set up in two modes; 'server' mode (which is
rather confusing I'll admit) and 'desktop' mode.  The major difference
between the two is that in 'desktop' mode it doesn't require you to login,
whereas 'server' mode is designed to be run on a separate machine and
accessed over the network requiring users to provide login credentials to
pgAdmin4 itself, in addition to any credentials needed to log into a
particular instance of postgreSQL.

So, if you are running on a constrained laptop, I would be careful to go
into your taskbar (assuming you are running Windows) and use the pgAdmin4
icon to stop the server when you are finished using it.  It will restart
the next time you try to run pgAdmin4.  Admittedly it would be helpful if
there was a setting that automatically stopped the pgAdmin4 server from
continuing to run after the last browser window was closed and it is
configured in 'desktop' mode.  Perhaps someday.

I hope that helps,

rik.

On Thu, Nov 12, 2020 at 4:24 PM mrivera  wrote:

> is there a way to not have a server start?  i have this on an older laptop
> and it does not say starting pgadmin4 server and is just a client.  I am
> trying to find a way for this new version on my new laptop to not start a
> server. Thank you for any assistance.
>
>
>
> --
> Sent from:
> https://www.postgresql-archive.org/PostgreSQL-pgadmin-support-f2191615.html
>
>
>

Re: pgAdmin 4 v4.28 released

[richard coleman]

👍


On Thu, Nov 12, 2020 at 11:22 AM Dave Page  wrote:

>
>
> On Thu, Nov 12, 2020 at 4:13 PM richard coleman <
> rcoleman.ascen...@gmail.com> wrote:
>
>> Dave,
>>
>> Thanks, but I expected that once an issue makes it into a release, and a
>> release announcement, that the veil is pulled back.
>>
>
> It has been - we just forgot with this one. There are a lot of moving
> parts in a release, and that's one that can't easily be automated.
>
>
>>
>> rik.
>>
>> On Thu, Nov 12, 2020 at 11:05 AM Dave Page  wrote:
>>
>>> Richard,
>>>
>>> On Thu, Nov 12, 2020 at 3:59 PM richard coleman <
>>> rcoleman.ascen...@gmail.com> wrote:
>>>
>>>> Hi All,
>>>>
>>>> The release notes list:
>>>>
>>>> Issue #5919 <https://redmine.postgresql.org/issues/5919> - Added
>>>> security related enhancements.
>>>>
>>>>
>>>> But this issue does not show up on the list of issues and following the
>>>> link returns a 403 error.  What exactly was included in this change?
>>>>
>>>
>>> The issue (like all security issues) was marked as private. We make the
>>> public following the release, which has now been done. The commit lists the
>>> following changes:
>>>
>>> Added following security enhancements:
>>> 1) Added ALLOWED_HOSTS list to limit the host address.
>>> 2) Added CSP and HSTS security header.
>>> 3) Hide the webserver/ development framework version.
>>>
>>>
>>>>
>>>> It doesn't seem exactly *transparent* that *secret* changes are being
>>>> made to this program.
>>>>
>>>
>>> We almost always make security changes in secret, in much the same way
>>> as other Open Source projects (e.g. PostgreSQL) do. That is to help protect
>>> users by not advertising potential vulnerabilities before fixes are
>>> available.
>>>
>>>
>>>
>>>>
>>>> Thanks,
>>>>
>>>> rik.
>>>>
>>>> On Thu, Nov 12, 2020 at 6:34 AM Akshay Joshi <
>>>> akshay.jo...@enterprisedb.com> wrote:
>>>>
>>>>> The pgAdmin Development Team is pleased to announce pgAdmin 4 version
>>>>> 4.28.
>>>>> This release of pgAdmin 4 includes 19 bug fixes and new features. For
>>>>> more details please see the release notes at:
>>>>>
>>>>> https://www.pgadmin.org/docs/pgadmin4/4.28/release_notes_4_28.html
>>>>> .
>>>>>
>>>>> pgAdmin is the leading Open Source graphical management tool for
>>>>> PostgreSQL. For more information, please see:
>>>>>
>>>>> https://www.pgadmin.org/
>>>>>
>>>>> Notable changes in this release include:
>>>>>
>>>>>- Added support to download utility files at the client-side.
>>>>>- Added support to rename query tool and debugger tabs title.
>>>>>- Added support for dynamic tab size.
>>>>>- Added tab title placeholder for Query Tool, View/Edit Data, and
>>>>>Debugger.
>>>>>- Added support to compare schemas and databases in schema diff.
>>>>>- Ensure that non-superuser should be able to debug the function.
>>>>>- Ensure that query history should be listed by date/time in
>>>>>descending order.
>>>>>- Ensure that Grant Wizard should include foreign tables.
>>>>>- Ensure that search object functionality works with case
>>>>>insensitive string.
>>>>>
>>>>>
>>>>> Builds for Windows and macOS are available now, along with a Python
>>>>> Wheel,
>>>>> Docker Container, RPM, DEB Package, and source code tarball from:
>>>>>
>>>>> https://www.pgadmin.org/download/
>>>>>
>>>>> --
>>>>> Akshay Joshi
>>>>> pgAdmin Project
>>>>>
>>>>>
>>>
>>> --
>>> Dave Page
>>> Blog: http://pgsnake.blogspot.com
>>> Twitter: @pgsnake
>>>
>>> EDB: http://www.enterprisedb.com
>>>
>>>
>
> --
> Dave Page
> Blog: http://pgsnake.blogspot.com
> Twitter: @pgsnake
>
> EDB: http://www.enterprisedb.com
>
>

Re: pgAdmin 4 v4.28 released

[richard coleman]

Dave,

Thanks, but I expected that once an issue makes it into a release, and a
release announcement, that the veil is pulled back.

rik.

On Thu, Nov 12, 2020 at 11:05 AM Dave Page  wrote:

> Richard,
>
> On Thu, Nov 12, 2020 at 3:59 PM richard coleman <
> rcoleman.ascen...@gmail.com> wrote:
>
>> Hi All,
>>
>> The release notes list:
>>
>> Issue #5919 <https://redmine.postgresql.org/issues/5919> - Added
>> security related enhancements.
>>
>>
>> But this issue does not show up on the list of issues and following the
>> link returns a 403 error.  What exactly was included in this change?
>>
>
> The issue (like all security issues) was marked as private. We make the
> public following the release, which has now been done. The commit lists the
> following changes:
>
> Added following security enhancements:
> 1) Added ALLOWED_HOSTS list to limit the host address.
> 2) Added CSP and HSTS security header.
> 3) Hide the webserver/ development framework version.
>
>
>>
>> It doesn't seem exactly *transparent* that *secret* changes are being
>> made to this program.
>>
>
> We almost always make security changes in secret, in much the same way as
> other Open Source projects (e.g. PostgreSQL) do. That is to help protect
> users by not advertising potential vulnerabilities before fixes are
> available.
>
>
>
>>
>> Thanks,
>>
>> rik.
>>
>> On Thu, Nov 12, 2020 at 6:34 AM Akshay Joshi <
>> akshay.jo...@enterprisedb.com> wrote:
>>
>>> The pgAdmin Development Team is pleased to announce pgAdmin 4 version
>>> 4.28.
>>> This release of pgAdmin 4 includes 19 bug fixes and new features. For
>>> more details please see the release notes at:
>>>
>>> https://www.pgadmin.org/docs/pgadmin4/4.28/release_notes_4_28.html.
>>>
>>> pgAdmin is the leading Open Source graphical management tool for
>>> PostgreSQL. For more information, please see:
>>>
>>> https://www.pgadmin.org/
>>>
>>> Notable changes in this release include:
>>>
>>>- Added support to download utility files at the client-side.
>>>- Added support to rename query tool and debugger tabs title.
>>>- Added support for dynamic tab size.
>>>- Added tab title placeholder for Query Tool, View/Edit Data, and
>>>Debugger.
>>>- Added support to compare schemas and databases in schema diff.
>>>- Ensure that non-superuser should be able to debug the function.
>>>- Ensure that query history should be listed by date/time in
>>>descending order.
>>>- Ensure that Grant Wizard should include foreign tables.
>>>- Ensure that search object functionality works with case
>>>insensitive string.
>>>
>>>
>>> Builds for Windows and macOS are available now, along with a Python
>>> Wheel,
>>> Docker Container, RPM, DEB Package, and source code tarball from:
>>>
>>> https://www.pgadmin.org/download/
>>>
>>> --
>>> Akshay Joshi
>>> pgAdmin Project
>>>
>>>
>
> --
> Dave Page
> Blog: http://pgsnake.blogspot.com
> Twitter: @pgsnake
>
> EDB: http://www.enterprisedb.com
>
>

Re: pgAdmin 4 v4.28 released

[richard coleman]

Hi All,

The release notes list:

Issue #5919  - Added security
related enhancements.


But this issue does not show up on the list of issues and following the
link returns a 403 error.  What exactly was included in this change?

It doesn't seem exactly *transparent* that *secret* changes are being made
to this program.

Thanks,

rik.

On Thu, Nov 12, 2020 at 6:34 AM Akshay Joshi 
wrote:

> The pgAdmin Development Team is pleased to announce pgAdmin 4 version 4.28.
> This release of pgAdmin 4 includes 19 bug fixes and new features. For
> more details please see the release notes at:
>
> https://www.pgadmin.org/docs/pgadmin4/4.28/release_notes_4_28.html.
>
> pgAdmin is the leading Open Source graphical management tool for
> PostgreSQL. For more information, please see:
>
> https://www.pgadmin.org/
>
> Notable changes in this release include:
>
>- Added support to download utility files at the client-side.
>- Added support to rename query tool and debugger tabs title.
>- Added support for dynamic tab size.
>- Added tab title placeholder for Query Tool, View/Edit Data, and
>Debugger.
>- Added support to compare schemas and databases in schema diff.
>- Ensure that non-superuser should be able to debug the function.
>- Ensure that query history should be listed by date/time in
>descending order.
>- Ensure that Grant Wizard should include foreign tables.
>- Ensure that search object functionality works with case insensitive
>string.
>
>
> Builds for Windows and macOS are available now, along with a Python Wheel,
> Docker Container, RPM, DEB Package, and source code tarball from:
>
> https://www.pgadmin.org/download/
>
> --
> Akshay Joshi
> pgAdmin Project
>
>

Re: pgAdmin 4 v4.28 released

[richard coleman]

Hi All,

The release notes list:

Issue #5919  - Added security
related enhancements.


But this issue does not show up on the list of issues and following the
link returns a 403 error.  What exactly was included in this change?

It doesn't seem exactly *transparent* that *secret* changes are being made
to this program.

Thanks,

rik.

On Thu, Nov 12, 2020 at 6:34 AM Akshay Joshi 
wrote:

> The pgAdmin Development Team is pleased to announce pgAdmin 4 version 4.28.
> This release of pgAdmin 4 includes 19 bug fixes and new features. For
> more details please see the release notes at:
>
> https://www.pgadmin.org/docs/pgadmin4/4.28/release_notes_4_28.html.
>
> pgAdmin is the leading Open Source graphical management tool for
> PostgreSQL. For more information, please see:
>
> https://www.pgadmin.org/
>
> Notable changes in this release include:
>
>- Added support to download utility files at the client-side.
>- Added support to rename query tool and debugger tabs title.
>- Added support for dynamic tab size.
>- Added tab title placeholder for Query Tool, View/Edit Data, and
>Debugger.
>- Added support to compare schemas and databases in schema diff.
>- Ensure that non-superuser should be able to debug the function.
>- Ensure that query history should be listed by date/time in
>descending order.
>- Ensure that Grant Wizard should include foreign tables.
>- Ensure that search object functionality works with case insensitive
>string.
>
>
> Builds for Windows and macOS are available now, along with a Python Wheel,
> Docker Container, RPM, DEB Package, and source code tarball from:
>
> https://www.pgadmin.org/download/
>
> --
> Akshay Joshi
> pgAdmin Project
>
>

Re: pgAdmin standalone

[richard coleman]

Msciwoj,

Just a word of warning, this *isn't* what you might suspect.  The old
desktop version had its own bundled browser frontend.  The current version,
even the _desktop_ version, is still a local web server that requires a web
browser to function as the UI.

rik.


On Wed, Oct 7, 2020 at 6:43 AM matshyeq  wrote:

> Hello,
>
> I Just noticed the main web doc says:
> "*A desktop runtime written in C++ with Qt allows it to run standalone
> for individual users*"
> Where do I get that standalone app?
> Is it available for MacOS?
> Thank you
> Best Regards
> ~Msciwoj
>

Re: pgAdmin 4 v4.26 released

[richard coleman]

Dave,

Thanks for the update.  Are you going to rerelease the update with a valid
certificate, or at least publish the SHA256 hash for the file so that we
can verify that it downloaded correctly?

Thanks again,

rik.

On Fri, Sep 18, 2020 at 4:45 AM Dave Page  wrote:

> Hi
>
> On Thu, Sep 17, 2020 at 4:22 PM Dave Page  wrote:
>
>>
>>
>> On Thu, Sep 17, 2020 at 4:18 PM richard coleman <
>> rcoleman.ascen...@gmail.com> wrote:
>>
>>> Akshay,
>>>
>>> Just downloaded pgadmin4-4.26-x64.exe from the official web site.  When
>>> I go to install it comes up with an "unknown publisher".
>>>
>>> Is this legit?
>>>
>>
>> I'm seeing that too - there doesn't seem to be a digital signature on the
>> installer.
>>
>
> So to the original question, yes, it is legit. The certificate expired :-(
>
>
>>
>> I have to wonder a) how that happened without the build failing,
>>
>
> That happened because all our build scripts will ignore certificate not
> found type errors, throwing out a warning to the (very long) build log
> instead. Microsoft's tools don't give a separate error for expired
> certificates - they have a generic "No suitable certificate found" one.
>
> It does it that way because individual developers don't have code signing
> certificates (they're expensive, a pain to get, and we don't want random
> ones with our name on them in existence, or to have lots of people with
> access to the one we use). Obviously the developers need to be able to
> build, even though they don't have a CSC.
>
> --
> Dave Page
> Blog: http://pgsnake.blogspot.com
> Twitter: @pgsnake
>
> EDB: http://www.enterprisedb.com
>
>

Re: pgAdmin 4 v4.26 released

[richard coleman]

Akshay,

Just downloaded pgadmin4-4.26-x64.exe from the official web site.  When I
go to install it comes up with an "unknown publisher".

Is this legit?

Thanks,

rik.

On Thu, Sep 17, 2020 at 8:09 AM Akshay Joshi 
wrote:

> The pgAdmin Development Team is pleased to announce pgAdmin 4 version 4.26.
> This release of pgAdmin 4 includes 30 bug fixes and new features. For
> more details please see the release notes at:
>
> https://www.pgadmin.org/docs/pgadmin4/4.26/release_notes_4_26.html.
>
> pgAdmin is the leading Open Source graphical management tool for
> PostgreSQL. For more information, please see:
>
> https://www.pgadmin.org/
>
> Notable changes in this release include:
>
>- Added SQL Formatter support in Query Tool.
>- Added a new button to the query tool toolbar to open a new query
>tool window.
>- Added shared server support for admin users.
>- Warn the user when connecting to a server that is older than pgAdmin
>supports.
>- Ensure that schema names starting with 'pg' should be visible in the
>browser tree when standard_conforming_strings is set to off.
>- Fixed an issue where --load-server does not allow loading
>connections that use pg_services.
>- Fixed string indices must be integers issue for PostgreSQL < 9.3.
>- Fixed an issue where the application ignores the fixed port
>configuration value.
>- Remove the illegal argument from the trigger function in the trigger
>DDL statement.
>- Ensure that 'setup-web.sh' should work in Debian 10.
>- Fixed excessive CPU usage by stopping the indefinite growth of the
>graph dataset.
>
>
> Builds for Windows and macOS are available now, along with a Python Wheel,
> Docker Container, RPM, DEB Package, and source code tarball from:
>
> https://www.pgadmin.org/download/
>
> --
> Akshay Joshi
> pgAdmin Project
>

Re: pgadmin 4.25 version - fix port number

[richard coleman]

Polgár,

Well that is annoying.  I was just wondering if it was related to bug #5783
( https://redmine.postgresql.org/issues/5783#change-23810 ).  You should
probably gile a bug report in the redmine system.

Best of luck,

rik.

On Tue, Sep 1, 2020 at 4:26 PM Polgár Benedek 
wrote:

> Dear Rik,
>
>
>
> I set 58505 port number in configure menu.
>
>
>
> When start pgadmin 4 server, it generate random port number, for example:
> 59860
>
> When use "new pgadmin4 window" from taskbar, use the previous random port
> number, 59860
>
>
>
> But i want that the pgadmin 4 server use the 58505 port number.
>
>
>
> Every time, when start pgadmin 4 server (after OS restart, or pagadmin
> server stop), it generate other random port number.
>
>
>
> *___*
>
> *Best Regards:*
>
>
>
> *Benedek Polgár | *System administrator | polgar.bene...@otpmobil.com
>
>
>
>
>
> *From:* richard coleman 
> *Sent:* 01 September 2020 21:43
> *To:* Polgár Benedek 
> *Cc:* pgadmin-support@lists.postgresql.org
> *Subject:* Re: pgadmin 4.25 version - fix port number
>
>
>
>
> Polgár,
>
>
>
> When you first start pgAdmin?
>
> When you use the "New pgAdmin 4 window..." option from the taskbar?
>
> Or both?
>
>
>
> Thanks,
>
>
>
> rik.
>
>
>
> On Tue, Sep 1, 2020 at 3:33 PM Polgár Benedek 
> wrote:
>
> Dear Support Team!
>
>
>
> The fixed port number config is not working in pgadmin 4.25 version.
>
> Please help me!
>
> Thank you!
>
>
>
> Attached printscreen.
>
>
>
> *___*
>
> *Best Regards:*
>
>
>
> *Benedek Polgár | *System administrator | polgar.bene...@otpmobil.com
>
>
>
>
>
>

Re: pgadmin 4.25 version - fix port number

[richard coleman]

Polgár,

When you first start pgAdmin?
When you use the "New pgAdmin 4 window..." option from the taskbar?
Or both?

Thanks,

rik.

On Tue, Sep 1, 2020 at 3:33 PM Polgár Benedek 
wrote:

> Dear Support Team!
>
>
>
> The fixed port number config is not working in pgadmin 4.25 version.
>
> Please help me!
>
> Thank you!
>
>
>
> Attached printscreen.
>
>
>
> *___*
>
> *Best Regards:*
>
>
>
> *Benedek Polgár | *System administrator | polgar.bene...@otpmobil.com
>
>
>
>
>

Re: Critical bug: pgAdmin v4.25 has started ignoring my "Browser Command" which completely cripples me and makes me unable to manage my PostgreSQL database.

[richard coleman]

That's what I do.

Chromium for pgAdmin4, Chrome, Vivaldi, Firefox for everything else.

¯\_(ツ)_/¯

rik.

On Wed, Aug 26, 2020 at 5:00 PM Jack Royal-Gordon  wrote:

> Here’s a thought that I think could solve your issues:
>
> It sounds like a lot of your issues are caused by the insistence on using
> PaleMoon. I don’t imagine that the team does much if any testing against
> PaleMoon, so I’m not shocked that you have issues with it. And I get it -
> you want private browsing. Why don’t you use Chrome for pgAdmin, and use
> PaleMoon for everything else? I don’t imagine that Chrome’s “spying” would
> be an issue for you with pgAdmin. Are you thinking that they’re going to
> monitor the databases you are administering?
>
> On Aug 26, 2020, at 10:32 AM, tutilu...@tutanota.com wrote:
>
> Aug 25, 2020, 2:59 PM by dp...@pgadmin.org:
>
>
>
> On Fri, Aug 21, 2020 at 11:23 AM  wrote:
>
>
> Please consider testing your software before releasing it.
>
>
> https://pgsnake.blogspot.com/2020/08/testing-pgadmin.html
>
>
> This certainly convinces me that there is quite a lot of testing
> happening, so that's at least reassuring in some sense. However, since it's
> necessary (in practice) to create a separate, dedicated browser profile for
> pgAdmin (since otherwise, it forgets the entire "state" every time you
> clear your browser data or close the browser, which happens constantly),
> breaking the "browser command" in a new version is quite remarkable.
>
> Also, it should be noted that my found work-around, to find the pgAdmin
> icon in the Notification area, right click it and then click "New pgAdmin
> window", only works once you are actually running it. When I start my
> machine, pgAdmin isn't running, so I first have to launch it using my
> normal Taskbar icon, which up until the latest version opened the correct
> pgAdmin browser profile. Now, it instead loads for some time and finally
> opens in the default browser (obviously with forgotten "state"). I then
> have to close it and then start it with the Notification area work-around.
>
> Yes, I could make it run on boot, to save myself another click and some
> waiting, but again, the problem isn't that I cannot find a way at all to
> use pgAdmin -- the issue is that such an "obvious" thing broke. It really
> makes me wonder how anyone could be running pgAdmin in their standard
> browser profile. I guess they never or rarely clear their browser data and
> never have to close all browser windows. I frequently need to do that for
> many reasons besides privacy, including updates, freezes/crashes (most
> frequently caused by pgAdmin, ironically), getting the "right order" of
> grouped windows of different browser profiles, etc.
>
> As I explained previously, it's impossible for me to use a "supported
> browser" because Chrome (and all its "skins" which pretend to be browsers)
> as well as Firefox are pure spyware. I don't say that without reason, but
> I'm not going to go into detail about that again here. At the end of the
> day, I'm forced to use Pale Moon or nothing at this point, and pgAdmin
> either hangs entirely or freezes for many, many seconds (half a minute or
> more is not uncommon) if I forget myself and try to click and resize the
> object tree pane to make me able to see what it contains. I have to
> actively remember to just scroll horizontally or else I can say "good bye"
> to that entire pgAdmin session. Which has many times caused loss of
> work/state for me. The same thing happens even if I just maximize/restore
> the window. The most likely cause is some JavaScript code used to "redraw"
> or "recalculate" the view.
>
> As you can see, I have extremely good reasons for wanting pgAdmin to ship
> with its own GUI/webview, and I frankly don't understand the stated reasons
> for why this is not done. I don't think you're lying, but NW.js (for
> example) uses Chrome/Chromium's engine and should not be possible to have
> any issues rendering and handling pgAdmin on all supported OSes. (I don't
> mention Electron because its developer is extremely toxic.)
>
> Yes, I'm aware that pgAdmin can be run in a "hosted" manner, so it still
> has to support "other browsers" (whatever that means at this point with
> Google's engine having a total monopoly besides a minimal Firefox and
> Safari user base), but then you could at least say that there's always the
> option to download the "stand-alone" version of pgAdmin which comes with a
> nice GUI/webview and never has to interfere in any way with existing
> browsers and all the nightmares that entails.
>
> The fact that you, the developers, don't see this as the #1 priority makes
> me wonder how it's possible that my "workflow" is apparently so
> fundamentally different from yours. Note that I'm not bashing the entire
> concept of "web apps", as this is what I have the most experience with
> myself, but simply the reluctance of packaging it in such a manner that it
> can be used without piggybacking on other software.
>

Re: Critical bug: pgAdmin v4.25 has started ignoring my "Browser Command" which completely cripples me and makes me unable to manage my PostgreSQL database.

[richard coleman]

Dave,

Thanks for the link.  It was very informative.  Best wishes to you and your
team.

rik.

On Tue, Aug 25, 2020 at 9:00 AM Dave Page  wrote:

>
>
> On Fri, Aug 21, 2020 at 11:23 AM  wrote:
>
>
>> Please consider testing your software before releasing it.
>>
>
> https://pgsnake.blogspot.com/2020/08/testing-pgadmin.html
>
> --
> Dave Page
> Blog: http://pgsnake.blogspot.com
> Twitter: @pgsnake
>
> EDB: http://www.enterprisedb.com
>
>

Re: Bug report: pgAdmin takes selected portion of query in Query Editor to run

[richard coleman]

Jack,

It's fine as it is once you get used to it.  For more involved or
complicated queries I use another tool that gives me the option to either:

"Run Script", which runs the entire query window
"Run Statement", which has the benefit of running the selected text OR (and
this is the part I really like) the statement that your cursor is currently
on, even if nothing is selected.

When I am developing complicated multi statement queries and only want to
test or run a single statement, I don't even have to select anything. ;)

I am finding that pgAdmin4 is a good tool for quick and dirty work with the
database, but this other tool is much more feature rich and so better for
doing more complicated work.

rik.




On Wed, Aug 12, 2020 at 3:43 PM Jack Royal-Gordon  wrote:

> I don’t know if it’s even a good idea to change that functionality. When
> I’m working on performance issues, I very well may put a very complicated
> SQL statement with several sub-selects in the window, and start with just
> one of the sub-selects to see what it’s performance issues might be. So
> it’s not unusual to select a piece of a statement and execute it.
>
> The behavior described by Tung Do is really just a learning step.
>
> On Aug 12, 2020, at 12:36 PM, richard coleman 
> wrote:
>
> That's not a bug, it's a *feature* !!
>
> Seriously though, presently the query window in pgAdmin4 has two options:
> If nothing is selected -> run the entire window
> If something is selected -> run just what's selected.
>
> That's how it's been since, well as long as I can recall.  Unlike some
> other tools, pgAdmin4 lacks the ability to "Run Selected" vs. "Run Entire
> Query Window", so it implements the previously mentioned logic.
>
> So I guess what you should probably do is create a *feature* request for
> this additional functionality.
>
> rik.
>
> On Wed, Aug 12, 2020 at 3:18 PM Trung Do  wrote:
>
>> If I enter a well formed SQL query into the Query Editor, but only
>> select a portion of the query with the mouse and try to run, pgAdmin
>> will try to run the selected portion as the query (and will fail most
>> of the time because of syntax error)
>>
>>
>>
>

Re: Bug report: pgAdmin takes selected portion of query in Query Editor to run

[richard coleman]

That's not a bug, it's a *feature* !!

Seriously though, presently the query window in pgAdmin4 has two options:
If nothing is selected -> run the entire window
If something is selected -> run just what's selected.

That's how it's been since, well as long as I can recall.  Unlike some
other tools, pgAdmin4 lacks the ability to "Run Selected" vs. "Run Entire
Query Window", so it implements the previously mentioned logic.

So I guess what you should probably do is create a *feature* request for
this additional functionality.

rik.

On Wed, Aug 12, 2020 at 3:18 PM Trung Do  wrote:

> If I enter a well formed SQL query into the Query Editor, but only
> select a portion of the query with the mouse and try to run, pgAdmin
> will try to run the selected portion as the query (and will fail most
> of the time because of syntax error)
>
>
>

Re: connect external app via pgadmin

[richard coleman]

B.,

I hate to be the bearer of bad news, but in a nutshell no.  As you write,
with both pgAdmin and postgreSQL installed on the same machine there is no
need to open any ports to access that particular postgreSQL instance.
Unfortunately unless the other application is also installed on that same
server AND had the ability to connect to postgreSQL without opening a port,
it won't be able to access postgreSQL either.

If you have postgreSQL and Qgis installed on the same server and Qgis is
configured to use postgreSQL internally, then if you open up the ports
needed to let the users use Qgis, you should be able to keep the postgreSQL
port closed to the outside world.  That's a lot of ifs and ands though.

I hope that helps,

rik.

On Wed, Aug 12, 2020 at 7:38 AM bw  wrote:

> I think you are missing the point Andrzej, my pgadmin and postgresql do
> run on the same server and there is no need to open up port 5432 externally
> or even internally and block access to the external world via the firewall
> as pgadmin is connected via the local socket. And I like to keep it that
> way hence my question :)
>
> ...but ... I like to give members that do have a pgadmin account the
> possibility to use their account to be able to connect via an external
> program like qgis.
>
> I like the maintenance to be as limited as possible so definitely not
> maintaining access via the pg_hda.conf or fiddling around with firewall
> regex rules for each user while they already have an pgadmin account.
>
> cheers. B
>
> On Wed, 12 Aug 2020 at 12:51, androxkentaki 
> wrote:
>
>> But pgAdmin runs at the same ports, so You need them to be opened.
>>
>> You can set in pgconf allowed IP pool.
>> You can change default port no por postgresql
>>
>> Maybe You can consider "hardware" solution: on Your gateway make in
>> firewall rule for specific IP address with port mapping/triggering
>> e.g. If Your pg is on default port 5432 make an rule that from if
>> somebody from external will try to connect via 87654 port will be
>> redirected to 5432
>>
>>
>> I don't know how Your infrastructure looks like so i can't give you more
>> detailed solution
>>
>> śr., 12 sie 2020 o 12:41 bw  napisał(a):
>>
>>> Andrzej,
>>>
>>> QGIS is just an example as I use it in combination with postgis in order
>>> to work in mapping GIS elements.
>>> With odbc I still need to open up the server ports to the outside world
>>> which is what I want to avoid.
>>>
>>> regards,
>>> Bastiaan
>>>
>>> On Wed, 12 Aug 2020 at 11:43, androxkentaki 
>>> wrote:
>>>
 i don't know what id Qgis and why You want to do it via pgAdmin...

 But did You consider using ODBC connection and its driver?

 śr., 12 sie 2020 o 08:58 bw  napisał(a):

> Hi,
>
> As I do not like to open-up my postgresql port to the outside world
> and managing users via pgadmin is very user friendly. I was wondering if
> somehow it would be possible to give external applications like Qgis for
> instance access to the database via pgadmin?
>
> For example in qgis in order to access the database it needs to
> connect directly to the postgresql port and I have to create a linux user
> for them. I do not want that. I rather manage this inside pgadmin. If qgis
> would somehow be able to connect to the db via a pgadmin api that would be
> really great.
>
> regards,
> Bastiaan
>


 --
 Z wyrazami szacunku
 Andrzej Gerasimuk

>>>
>>
>> --
>> Z wyrazami szacunku
>> Andrzej Gerasimuk
>>
>

Re: Mystery "PostgreSQL 11" server keeps reappearing in pgAdmin 4 no matter how many times I delete it.

[richard coleman]

Dave,

On Tue, Apr 21, 2020 at 4:31 AM Dave Page  wrote:

>
>
> On Tue, Apr 21, 2020 at 8:57 AM  wrote:
>
>> Ever since I went through the horrible ordeal of trying to update
>> PostgreSQL on Windows (from 11.5 to 11.7, so not even a major version),
>> pgAdmin 4 has started showing a "PostgreSQL 11" server in the list of
>> servers. I've deleted it a hundred times now, but it just keeps reappearing
>> every time I start pgAdmin 4.
>>
>
> I'm not sure how that would be a horrible ordeal. You just run the
> installer and it upgrades with a few clicks.
>

Well as someone who had the misfortune of upgrading an SQL_ASCII postgreSQL
9 instance to 10, I can sympathize.  Depending on the particulars, it's _a_
_lot_ more than just "a few clicks".

>
>
>>
>> What is this? How to *actually* remove it rather than "pretend-removing"
>> it? Why is it there at all? I never added any such server to pgAdmin 4, and
>> why would it keep adding it back?
>>
>
> Don't remove it. Rename it and/or change any settings you require, then
> delete the one you manually added.
>

Wouldn't it make more sense to have a setting to *not* try and auto-detect
existing postgreSQL instances?

>
>
>>
>> If trying to connect to it, it asks for a password. I enter none and
>> connect. It seems to be an identical copy of the actual server. In the
>> comments, it says:
>>
>> Auto-detected PostgreSQL 11 installation with the data directory at
>> C:\Users\blablabla...
>>
>> Okay, so pgAdmin 4 auto-detected what I already have as a named server in
>> the list, and keeps adding it back? I don't understand the point.
>> Especially the part where it keeps reappearing when I delete it.
>>
>
> It doesn't know that the server you added is the same connection; you
> might intentionally have the same server added twice, but with subtle
> differences in the settings. It keeps track of the ID of the server from
> the registry, and if it finds a server listed in the registry doesn't
> exist, it'll auto-add it (and store the ID so it doesn't duplicate it
> itself).
>
> Correct, and since it has no way of knowing, shouldn't it be up to the
user to decide as opposed to forcing the user to work around quirk of the
application?

rik.

> --
> Dave Page
> Blog: http://pgsnake.blogspot.com
> Twitter: @pgsnake
>
> EnterpriseDB UK: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>

Re: Proposal: Drop support for Internet Explorer

[richard coleman]

Dave,

Seeing that IE isn't standards compliant and not only is not being further
developed, but Microsoft is actively discouraging its use, it is probably
time to drop support for it.

I would caution *against* using browser analytics as any sort of proxy for
use.  Since pgAdmin 4 lacks a UI of its own, I rely on an instance of
Chromium (or Vivalidi, or Firefox, depending on the machine) to run pgAdmin
under.  In every case, the browser that I am *running* pgAdmin 4 under is
*not* the same browser that I use to browse websites, and so would never
show up in your analytics.

Just something to keep in mind,

rik.

On Tue, Apr 7, 2020 at 8:00 AM Dave Page  wrote:

>
>
> On Tue, Apr 7, 2020 at 12:41 PM Dave Caughey  wrote:
>
>> Check the analytics... I think you'll find dropping it is a non-issue. In
>> my own web service, I found that IE (all versions) constituted only about
>> 1% of my users.
>>
>
> Good point - 1.9% of the visitors to the website were on IE this week. 1.8
> of those were on IE11. We even had one hit from IE5...
>
> By comparison, 72% of users were on Chrome, 13% on Firefox, with 5.5% each
> for Safari and Edge.
>
>
>>
>> So I dropped support for IE (since it was preventing me from fully
>> adopting ES6), and there was not a single complaint from my users.
>>
>> Cheers,
>> Dave
>>
>> On Tue., Apr. 7, 2020, 3:36 a.m. Dave Page,  wrote:
>>
>>> All,
>>>
>>> Internet Explorer has long been superseded by Microsoft Edge, and even
>>> that has recently moved to using Chromium as it's core engine. Version 11
>>> was originally released in 2013, and though Microsoft have committed to
>>> supporting it until 2025, as far as I can tell there have been no notable
>>> new features in almost it's entire lifetime, and certainly in recent years
>>> Microsoft have only been releasing security fixes.
>>>
>>> As you can imagine, supporting Internet Explorer has a non-trivial cost
>>> to it for the pgAdmin project. Not only do we need to test with it as well
>>> as Edge, but we also need to write code, CSS and HTML that is fully
>>> compatible with what essentially is a 7 year old browser. By comparison,
>>> for all other browsers we typically aim to support releases no more than 2
>>> years old.
>>>
>>> I therefore propose that we officially drop support for Internet
>>> Explorer. Practically this means that we would not test with it, and anyone
>>> reporting a bug with it would be told to use an alternate browser.
>>>
>>> Objections/comments please?
>>>
>>> Thanks!
>>>
>>> --
>>> Dave Page
>>> Blog: http://pgsnake.blogspot.com
>>> Twitter: @pgsnake
>>>
>>> EnterpriseDB UK: http://www.enterprisedb.com
>>> The Enterprise PostgreSQL Company
>>>
>>
>
> --
> Dave Page
> Blog: http://pgsnake.blogspot.com
> Twitter: @pgsnake
>
> EnterpriseDB UK: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>

Re: Starting just the pgAdmin server

[richard coleman]

Ken,

Short answer, it's a more or less a self contained environment for running
applications.  Docker  is more developer friendly,
a similar technology kubernetes  is more dev ops
focused.

Here are a few links to get you started:

   - https://hub.docker.com/r/dpage/pgadmin4/
   - https://www.pgadmin.org/docs/pgadmin4/latest/container_deployment.html
   - https://www.pgadmin.org/download/pgadmin-4-container/

Enjoy,

rik.

On Fri, Apr 3, 2020 at 10:00 AM Ken Benson  wrote:

>
>
> *From:* Brian Wilson 
> *Sent:* Thursday, April 2, 2020 9:52 AM
> *To:* George Weaver 
> *Cc:* pgadmin-supp...@postgresql.org
> *Subject:* Re: Starting just the pgAdmin server
>
>
>
> My advice to anyone using pgadmin4 is to try running it in Docker.
>
> I replied privately to George with more details. I can forward all that
> here if people want.
>
> You might end up using Docker only for pgadmin4 but once you get used to
> using it I think it will be a valuable tool for you. The longer I use it
> the more places it fits in.
>
>
>
> *[Ken Benson] *
>
> *I’m curious – what is Docker and where can I find some information on
> running PgAdmin 4 in Docker?*
>
>
>
> Ken Benson | ken @ infowerks-dot-com
>
>
>
>
>
> Brian
>
>
>
>
>
>
>

Re: Seriously? MASTER PASSWORD REQUIRED Again?!#$@!

[richard coleman]

Dave,

On Fri, Oct 18, 2019 at 3:24 AM Dave Page  wrote:

>
>
> On Thu, Oct 17, 2019 at 7:03 PM richard coleman <
> rcoleman.ascen...@gmail.com> wrote:
>
>> Aditya,
>>
>> That's new.  I have kept that setting in that file ever since the it was
>> introduced.  This is the *first* time it's been removed.
>>
>
> Then you must not have been using one of our packages. If memory serves,
> you run on Windows, in which the code to write a platform-specific
> config_distro.py with every installation/upgrade on Windows was added on 16
> June 2016:
>
>
> https://git.postgresql.org/gitweb/?p=pgadmin4.git;a=commitdiff;h=931f671756d43ea7d22d460fcb4c7a815a5aad11
>

Actually I run it on Kubuntu *and* Windows 10.  This instance was on
Windows 10, downloaded from the page the automatic updater takes you to:
https://www.pgadmin.org/download/pgadmin-4-windows/.

At least the APT (.deb) file has the decency to warn you when the package
manager wants to blindly wipe out a config file you've updated. 'Replace
with the new one', 'Keep your existing one', 'See the changes between the
two before you make up your mind'.  With the default being to leave your
config file alone.  The Windows installer should at least do the same.


>> Documentation of Master Password feature:
>> https://www.pgadmin.org/docs/pgadmin4/development/master_password.html
>>
>> Link to Desktop deployment from that page:
>>
>> https://www.pgadmin.org/docs/pgadmin4/development/desktop_deployment.html#desktop-deployment
>>
>> Relevant section of config*.py files:
>> (
>> https://www.pgadmin.org/docs/pgadmin4/development/config_py.html#config-py
>> ):
>>
>> There are multiple configuration files that are read at startup by
>> pgAdmin. These are as follows:
>>
>>- config.py: This is the main configuration file, and should not be
>>modified. It can be used as a reference for configuration settings, that
>>may be overridden in one of the following files.
>>- config_distro.py: This file is read after config.py and is intended
>>for packagers to change any settings that are required for their pgAdmin
>>distribution. This may typically include certain paths and file locations.
>>This file is optional, and may be created by packagers in the same
>>directory as config.py if needed.
>>- config_local.py: This file is read after config_distro.py and is
>>intended for end users to change any default or packaging specific 
>> settings
>>that they may wish to adjust to meet local preferences or standards.This
>>file is optional, and may be created by users in the same directory as
>>config.py if needed.
>>
>> Can you point out the section that states config_distro.py will be
>> overwritten on upgrade (I can't seem to find it)?
>>
>
> It doesn't - much as it doesn't say that any of the other few hundred
> files we install may be updated.
>

None of the other hundreds of files that might be updated contain settings
that the end user is supposed to make changes in.

>
> What it does clearly say is that the config_distro,py is for use by
> *packagers* and config_local.py is for use by *end users*.
>

That would be just a wee more helpful if you actually *included* a
*config_local.py* in that directory for users to update, or better yet,
didn't require users to make changes to config files and just kept the
settings in the Preferences UI, as you have done with *ALL* the others
settings a user might be interested in changing.

>
>
>>
>> Can you explain *why* it just started replacing (in in the process
>> removing the MASTER_PASSWORD_REQUIRED = False statement) it in the 4.14
>> upgrade, but not before?
>>
>> Thanks,
>>
>> rik.
>>
>>
>> On Thu, Oct 17, 2019 at 12:50 PM Aditya Toshniwal <
>> aditya.toshni...@enterprisedb.com> wrote:
>>
>>> Hi Richard,
>>>
>>> You need to add the setting in config_local.py. Other files will be
>>> replaced except config_local.py.
>>>
>>> On Thu, Oct 17, 2019, 22:15 richard coleman 
>>> wrote:
>>>
>>>> Ugg,
>>>>
>>>> Just upgraded pgAdmin4 to the latest version 4.14.  Even though I have
>>>> had the Master Password requirement disabled for as long as it has been in
>>>> existence, guess what I was greeted with upon starting pgAdmin4?  If you
>>>> guessed the prompt requiring me to create a Master Password, or be locked
>>>> out of the UI, give yourself a prize.
>>>>
>>>> Seriously people, I don't want/need a Master Password.  Not now, not
>>>> *ever.*
>>>>
>>>> I've added the required incantation:
>>>>
>>>> MASTER_PASSWORD_REQUIRED = False
>>>>
>>>>
>>>> *back* into the *config.distro.py <http://config.distro.py>* yet again.
>>>>
>>>> Can you please *stop* trying to force this on me (and anyone else who
>>>> has no need for it)?
>>>>
>>>> Thanks,
>>>>
>>>> rik.
>>>>
>>>
>
> --
> Dave Page
> Blog: http://pgsnake.blogspot.com
> Twitter: @pgsnake
>
> EnterpriseDB UK: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>

rik.

Re: Seriously? MASTER PASSWORD REQUIRED Again?!#$@!

[richard coleman]

Aditya,

That's new.  I have kept that setting in that file ever since the it was
introduced.  This is the *first* time it's been removed.

Documentation of Master Password feature:
https://www.pgadmin.org/docs/pgadmin4/development/master_password.html

Link to Desktop deployment from that page:
https://www.pgadmin.org/docs/pgadmin4/development/desktop_deployment.html#desktop-deployment

Relevant section of config*.py files:
( https://www.pgadmin.org/docs/pgadmin4/development/config_py.html#config-py
):

There are multiple configuration files that are read at startup by pgAdmin.
These are as follows:

   - config.py: This is the main configuration file, and should not be
   modified. It can be used as a reference for configuration settings, that
   may be overridden in one of the following files.
   - config_distro.py: This file is read after config.py and is intended
   for packagers to change any settings that are required for their pgAdmin
   distribution. This may typically include certain paths and file locations.
   This file is optional, and may be created by packagers in the same
   directory as config.py if needed.
   - config_local.py: This file is read after config_distro.py and is
   intended for end users to change any default or packaging specific settings
   that they may wish to adjust to meet local preferences or standards.This
   file is optional, and may be created by users in the same directory as
   config.py if needed.

Can you point out the section that states config_distro.py will be
overwritten on upgrade (I can't seem to find it)?

Can you explain *why* it just started replacing (in in the process removing
the MASTER_PASSWORD_REQUIRED = False statement) it in the 4.14 upgrade, but
not before?

Thanks,

rik.


On Thu, Oct 17, 2019 at 12:50 PM Aditya Toshniwal <
aditya.toshni...@enterprisedb.com> wrote:

> Hi Richard,
>
> You need to add the setting in config_local.py. Other files will be
> replaced except config_local.py.
>
> On Thu, Oct 17, 2019, 22:15 richard coleman 
> wrote:
>
>> Ugg,
>>
>> Just upgraded pgAdmin4 to the latest version 4.14.  Even though I have
>> had the Master Password requirement disabled for as long as it has been in
>> existence, guess what I was greeted with upon starting pgAdmin4?  If you
>> guessed the prompt requiring me to create a Master Password, or be locked
>> out of the UI, give yourself a prize.
>>
>> Seriously people, I don't want/need a Master Password.  Not now, not
>> *ever.*
>>
>> I've added the required incantation:
>>
>> MASTER_PASSWORD_REQUIRED = False
>>
>>
>> *back* into the *config.distro.py <http://config.distro.py>* yet again.
>>
>> Can you please *stop* trying to force this on me (and anyone else who has
>> no need for it)?
>>
>> Thanks,
>>
>> rik.
>>
>

Seriously? MASTER PASSWORD REQUIRED Again?!#$@!

[richard coleman]

Ugg,

Just upgraded pgAdmin4 to the latest version 4.14.  Even though I have had
the Master Password requirement disabled for as long as it has been in
existence, guess what I was greeted with upon starting pgAdmin4?  If you
guessed the prompt requiring me to create a Master Password, or be locked
out of the UI, give yourself a prize.

Seriously people, I don't want/need a Master Password.  Not now, not *ever.*

I've added the required incantation:

MASTER_PASSWORD_REQUIRED = False


*back* into the *config.distro.py * yet again.

Can you please *stop* trying to force this on me (and anyone else who has
no need for it)?

Thanks,

rik.

Sane right-click Hurray

[richard coleman]

Finally got 4.12 here, and I am pleasantly surprised to see a sane (and
some would say) sensible right-click context menu in the query tool.

Good job devs.

rik.

Re: Some pgAdmin bugs...

[richard coleman]

Dave,

While I agree it's generally a good idea to have a primary key, the
solution as currently implemented leaves the user unable to edit, or in
this case to even add a record to table without one.  I would suggest
either having pgAdmin4 compute some sort of an *internal key* for cases
like this, or in the alternative *disable* those features (such as View/
*Edit*) that have not been implemented for cases such as this.  Perhaps
with a dialog informing the user that "Editing or adding data isn't
supported on tables without a primary key".

rik.

On Tue, Sep 10, 2019 at 8:34 AM Dave Page  wrote:

>
>
> On Tue, Sep 10, 2019 at 8:24 AM richard coleman <
> rcoleman.ascen...@gmail.com> wrote:
>
>> Hi All,
>>
>> My $0.02.  Tested the first one here (Kubuntu 18.04, Chromium, pgAdmin 4
>> 4.12) with mixed results.
>>
>> On Tue, Sep 10, 2019 at 7:59 AM Aditya Toshniwal <
>> aditya.toshni...@enterprisedb.com> wrote:
>>
>>> Hi,
>>>
>>> On Tue, Sep 10, 2019 at 5:13 PM Arni Kromić 
>>> wrote:
>>>
>>>> Working with pgAdmin, I've found several bugs. Not sure if they are
>>>> already reported; couldn't find them on Redmine, but perhaps I missed them.
>>>> Maybe someone will recognize if they've already been reported. Here it
>>>> goes...
>>>>
>>>> 1) When doing View/Edit on an empty table, I cannot insert anything
>>>> when it opens. There is no empty row I can write into, like there is when a
>>>> table has at least one row already. In fact, there are no rows at all, just
>>>> the header.
>>>>
>>> I tried. I get an empty row to enter
>>> [image: Screenshot 2019-09-10 at 17.25.25.png]
>>>
>>>
>> Test table0: two columns both character varying columns, no primary key,
>> View/Edit opens without any rows as the original poster Arni wrote.
>>
>> Test table1: three columns, two character varying, one primary key
>> bigint, View/Edit opens with a single blank row as Aditya reported.
>>
>> Does Arni's table have a primary key defined?  Is it a bigint?  It looks
>> like there might be a bug where pgAdmin4 isn't presenting a row to add a
>> record from the View/Edit function if there isn't a primary key, or a
>> particular type of primary key defined on the table.
>>
>
> If memory serves that was a design choice when the code was implemented.
> We cannot safely allow editing without a primary key, and adding rows
> (which arguably is safe) is considered editing as the code is currently
> implemented.
>
> I consider this a corner-case; typically one would have a primary key on a
> table to identify individual rows, and most cases where you wouldn't are
> probably not ones where you'd ever try to edit or manually add data
> (consider something like sensor output data). I'm not sure how much demand
> there would be for doing this; clearly not a huge amount.
>
> --
> Dave Page
> Blog: http://pgsnake.blogspot.com
> Twitter: @pgsnake
>
> EnterpriseDB UK: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>

Re: Some pgAdmin bugs...

[richard coleman]

Hi All,

My $0.02.  Tested the first one here (Kubuntu 18.04, Chromium, pgAdmin 4
4.12) with mixed results.

On Tue, Sep 10, 2019 at 7:59 AM Aditya Toshniwal <
aditya.toshni...@enterprisedb.com> wrote:

> Hi,
>
> On Tue, Sep 10, 2019 at 5:13 PM Arni Kromić 
> wrote:
>
>> Working with pgAdmin, I've found several bugs. Not sure if they are
>> already reported; couldn't find them on Redmine, but perhaps I missed them.
>> Maybe someone will recognize if they've already been reported. Here it
>> goes...
>>
>> 1) When doing View/Edit on an empty table, I cannot insert anything when
>> it opens. There is no empty row I can write into, like there is when a
>> table has at least one row already. In fact, there are no rows at all, just
>> the header.
>>
> I tried. I get an empty row to enter
> [image: Screenshot 2019-09-10 at 17.25.25.png]
>
>
Test table0: two columns both character varying columns, no primary key,
View/Edit opens without any rows as the original poster Arni wrote.

Test table1: three columns, two character varying, one primary key bigint,
View/Edit opens with a single blank row as Aditya reported.

Does Arni's table have a primary key defined?  Is it a bigint?  It looks
like there might be a bug where pgAdmin4 isn't presenting a row to add a
record from the View/Edit function if there isn't a primary key, or a
particular type of primary key defined on the table.

I hope that helps,

rik.

>

Re: Start pgadmin4 server

[richard coleman]

Khushboo,

Thanks for the thought, but I believe he is asking how to start
pgAdmin4 *without
*opening a browser window.  In other words, start pgAdmin4 but *never* see
a browser window until you choose "New pgAdmin 4 window ...".

I don't think that's possible, at least from the *desktop* variant of
pgAdmin4.  I would love to be shown to be wrong.

pgAdmin4 is still stuck between being a desktop application and a server
application.

rik.

On Mon, Aug 26, 2019 at 1:34 AM Khushboo Vashi <
khushboo.va...@enterprisedb.com> wrote:

> Hi,
>
> On Sat, Aug 24, 2019 at 2:40 PM Polgár Benedek <
> polgar.bene...@otpmobil.com> wrote:
>
>> Dear Support team!
>>
>>
>>
>> I use a chrome shortcut of pgadmin4, that I can manage the pgadmin4
>> software on windows taskbar.
>>
>> But This shortcut only works if first time I run pgadmin4.exe (this exe
>> start pgadmin4 server and open pgadmin4 client in chrome browser).
>>
> Once you start the server, you can see the pgAdmin 4 icon in the taskbar,
> even if you close the browser, the server will not be stopped.
> Right click on the pgadmin 4 taskbar icon (one with elephant icon) > Click
> on New pgAdmin 4 Window.
>
> Thanks,
> Khushboo
>
>>
>>
>> How can I start pgadmin4 server without open pgadmin4 client?
>>
>>
>>
>> *__*
>>
>> *Best Regardsl:*
>>
>>
>>
>> *Benedek Polgár*
>>
>> System administrator
>>
>>
>>
>> polgar.bene...@otpmobil.com
>>
>>
>>
>>
>>
>> 1093 Budapest, Közraktár u. 30-32.
>>
>> RiverPark, K30. épület, II. emelet
>>
>>
>>
>> 
>> 
>>
>>
>>
>

Re: pgAdmin 4 ignores its own config option: "BrowserCommand"

[richard coleman]

Tutiluren,

On Thu, Aug 8, 2019 at 6:16 PM  wrote:

> I don't know what you mean by right-clicking on the pgAdmin 4 Taskbar icon
> and selecting "Configure", because no such thing appears when I do that.
> The only other option other than running it is "Unpin".
>
> > Here are a few pictures (from Windows 10) that I hope will illustrate:
> the notification icon in the taskbar (the blue elephant, it might be
hidden)
[image: pgAdmin4_notification_icon.png]

>The context menu when you right-click that icon
[image: pgAdmin4_notification_context_menu.png]

>The dialog box that appears when you select 'Configure'
[image: pgAdmin4_configure_dialog.png]
 > and yes even though I took these on a Windows 10 machine (not my usual
one) the example string in the 'Browser Command' text box is linux/macOs.

As for the quotes around the path, it's required for the path to the
> Firefox.exe to be recognized properly. I did try without quotes around
> %URL%, though. Same thing. It doesn't run the command.
>
> I don't know what you mean by "it" in "I can't say whether or not it
> honors alternate profiles", but pgAdmin doesn't need to support anything
> whatsoever; it's all about what Firefox does with the command parameters...
> but that command is not being sent. pgAdmin 4 appears to be ignoring its
> own config setting.
>
> > *it* refers to pgAdmin4.  The question I was wondering about was
whether pgAdmin4 sends the complete browser command, or if the syntax was
somehow incorrect.

>
> 9 Aug 2019, 00:05 by rcoleman.ascen...@gmail.com:
>
> tutiluren,
>
> I am sorry to read that you are still having difficulties.  The
> MASTER_PASSWORD_REQUIRED string is documented in the pgAdmin4 documentation
> located here:
> https://www.pgadmin.org/docs/pgadmin4/development/master_password.html .
> As for the BrowserCommand I usually set it in the configure dialog that I
> get to by right clicking on the *elephant* taskbar icon and selecting
> "Configure".  My command is: *chromium-browser %URL% , *this is stored
> as:
>
> *BrowserCommand=chromium-browser %URL%*
>
> in my pgadmin4.conf file.  Notice there are *no* *"* around the
> arguments, unlike your string.  Yes, the config.py, config_distro.py and
> config_local.py all contain keywords in the
> ALL_CAPS_SEPARATED_BY_UNDERSCORES while the pgadmin4.config file uses
> MixedCaseAllRunTogether.  It is a bit inconsistent.
>
> I can't say whether or not it honors alternate profiles, as I just use an
> alternate *browser*, but perhaps it didn't like all of your quotes.
>
> I hope that helps,
>
> rik.
>
> On Thu, Aug 8, 2019 at 3:44 PM  wrote:
>
> Okay, so after 30 million years of searching and reading and swearing and
> cursing, I've finally found the "BrowserCommand" configuration directive.
> So I set my C:\Program Files (x86)\pgAdmin 4\v4\web\config_local.py to:
>
> MASTER_PASSWORD_REQUIRED=False
> BrowserCommand="C:\Program Files\Mozilla Firefox\firefox.exe" -p "pgAdmin"
> --no-remote "%URL%"
>
> But when I then click the pgAdmin 4 start icon ("C:\Program Files
> (x86)\pgAdmin 4\v4\runtime\pgAdmin4.exe"), it *still* opens Firefox
> (default browser) with the DEFAULT profile. In other words, it ignores my
> BrowserCommand, which tells it to open the URL in the "pgAdmin" profile,
> which I've spent significant efforts setting up just for pgAdmin 4, so that
> I can finally use the program without being constantly harassed for
> passwords and losing all my work whenever Firefox needs to be restarted.
>
> And no, there is nothing wrong with the command itself; I use it with
> other profiles. But pgAdmin is clearly ignoring it. What's wrong?
>
> Also, MASTER_PASSWORD_REQUIRED is undocumented on
> https://www.pgadmin.org/docs/pgadmin4/4.11/desktop_deployment.html , and
> doesn't use the same format (it would be MasterPasswordRequired if it were
> to follow the style of the other options)... What's up with that?
>
> > I hope that helps,
>

   > rik.

Re: pgAdmin 4 ignores its own config option: "BrowserCommand"

[richard coleman]

tutiluren,

I am sorry to read that you are still having difficulties.  The
MASTER_PASSWORD_REQUIRED string is documented in the pgAdmin4 documentation
located here:
https://www.pgadmin.org/docs/pgadmin4/development/master_password.html .
As for the BrowserCommand I usually set it in the configure dialog that I
get to by right clicking on the *elephant* taskbar icon and selecting
"Configure".  My command is: *chromium-browser %URL% , *this is stored as:

*BrowserCommand=chromium-browser %URL%*

in my pgadmin4.conf file.  Notice there are *no* *"* around the arguments,
unlike your string.  Yes, the config.py, config_distro.py and
config_local.py all contain keywords in the
ALL_CAPS_SEPARATED_BY_UNDERSCORES while the pgadmin4.config file uses
MixedCaseAllRunTogether.  It is a bit inconsistent.

I can't say whether or not it honors alternate profiles, as I just use an
alternate *browser*, but perhaps it didn't like all of your quotes.

I hope that helps,

rik.

On Thu, Aug 8, 2019 at 3:44 PM  wrote:

> Okay, so after 30 million years of searching and reading and swearing and
> cursing, I've finally found the "BrowserCommand" configuration directive.
> So I set my C:\Program Files (x86)\pgAdmin 4\v4\web\config_local.py to:
>
> MASTER_PASSWORD_REQUIRED=False
> BrowserCommand="C:\Program Files\Mozilla Firefox\firefox.exe" -p "pgAdmin"
> --no-remote "%URL%"
>
> But when I then click the pgAdmin 4 start icon ("C:\Program Files
> (x86)\pgAdmin 4\v4\runtime\pgAdmin4.exe"), it *still* opens Firefox
> (default browser) with the DEFAULT profile. In other words, it ignores my
> BrowserCommand, which tells it to open the URL in the "pgAdmin" profile,
> which I've spent significant efforts setting up just for pgAdmin 4, so that
> I can finally use the program without being constantly harassed for
> passwords and losing all my work whenever Firefox needs to be restarted.
>
> And no, there is nothing wrong with the command itself; I use it with
> other profiles. But pgAdmin is clearly ignoring it. What's wrong?
>
> Also, MASTER_PASSWORD_REQUIRED is undocumented on
> https://www.pgadmin.org/docs/pgadmin4/4.11/desktop_deployment.html , and
> doesn't use the same format (it would be MasterPasswordRequired if it were
> to follow the style of the other options)... What's up with that?
>

Re: My user experience with pgAdmin 4.

[richard coleman]

For what it's worth,

I try to mitigate the isolation issue by letting pgAdmin4 have it's own
dedicated browser.  I have a Chromium installation that is only used for
pgAdmin4.  I've adjusted the *browser command* to: "chromium-browser
%URL%".  In that way, whenever I start pgAdmin4, or ask for a new window,
I'll always get that Chromium install.

It's a bit *overkill *I know, but with pgAdmin4 not having it's own UI,
it's the least I can do to keep it away from the rest of my
browsing/developing.

Perhaps it might help you as well.

rik.

On Sun, Aug 4, 2019 at 11:36 PM Bill Evans  wrote:

> I think that the fundamental issue is that pgAdmin 3 was a stand-alone
> app, and, as such, supported a set of features. The big one here is
> isolation; the pgAdmin environment was unaffected by much outside of it.
>
> For good or for ill, the decision was taken to write a new admin program
> as a web page. To the extent that this requires running the admin in the
> “system browser”, isolation takes a big hit. It should be possible,
> desirable even, to build a fork of Chrome or Firefox that is dedicated to
> browsing pages from the admin server. That could certainly be done
> independently of the core pgAdmin 4 product. But that would be a pretty big
> project in itself.
>
> One easier suggestion would be to embrace the psql app. It is certainly
> not “the same thing”, that is true, but it is very powerful, and very
> useful, and is completely unaffected by whatever nonsense is going on in my
> browser. For some tasks, it is *much* easier than a GUI. And it starts up
> instantly.
>
> Just a thought.
>
> Sent from my iPad
>
> On Aug 4, 2019, at 4:43 PM, Robert Eckhardt  wrote:
>
> > On Mon, Aug 5, 2019 at 1:51 AM  wrote:
> >
> > Every day, whenever I want to administrate my PG databases, I click the
> pgAdmin 4 icon in the Taskbar. This causes a splash screen to start loading
> for a very long time (if it's the first time since the computer was started
> for the day) and eventually opens my normal browser (Firefox, which I don't
> even like, but it's the least horrible one left) with a new tab for pgAdmin
> 4.
> >
> > Now, even after disabling the "master password" stuff, I'm always forced
> to enter the password and pointlessly click the "remember" checkbox, only
> to be greeted with the same prompts every single day. This is because I
> (like any sane human) clears all browser data in Firefox many times a day.
> Which means pgAdmin 4 keeps forgetting the credentials, because it's
> piggybacking on Firefox and storing its settings in whatever manner Firefox
> does it, and then it's cleared constantly when I perform my routine privacy
> task.
> >
> > Even if it didn't do this, it would still be very awkward and bad for a
> multitude of reasons to have the database administration GUI as part of my
> normal web browser. It just seems fundamentally wrong to me. Whenever you
> need to restart the browser or clear all data/tabs, you lose your "state"
> in pgAdmin 4 and have to connect to it once again, starting all over. It
> truly cripples me.
> >
> > I get that it's *easier* for the developers to just ignore this
> fundamental problem, because they apparently don't use it themselves, or
> have very different "work flows", and everyone seems to be taking the
> "easy" way out these days, observable in virtually every aspect of life,
> but it doesn't make it less obnoxious for the user. At least for this user.
>
> I'm not quite sure what to make of this.
>
> You have basically written an email that says that your workflow
> cannot align with a browser based UI. There is not much to do here
> other than change your workflow or change to a UI that isn't browser
> based.
>
> All the downside and problems you have mentioned aren't product
> problems, they are tech restrictions that come from using a browser.
> If the need for a browser were dropped and pgAdmin was rewritten as a
> native client app then a different person could come in and simply
> write a similar email about all of the downsides inherent with a
> native app.
>
> >
> > I honestly have no idea who the pgAdmin 4 developers are, so it's
> nothing personal against them, but every day when I'm subjected to things
> like this, a certain hate grows within me toward whoever is responsible for
> making the bad decisions which affect me negatively. If the program had its
> own GUI and didn't harass me in all kinds of ways, I would instead
> constantly feel positive feelings toward the authors.
> >
> > The only reason I still care about pgAdmin 4 is that there is no
> alternative. I've spent countless hours researching the so-called
> "alternatives", and they all have some major show-stopper about them. This
> one at least feels like a "kind of" official project. I just wish it didn't
> make dealing with my PostgreSQL databases feel like such a chore.
>
> The question I have is; understanding that this is a browser based
> application. What could be done to improve your 

Re: pgadmin4 - Use classic style interface, don't launch browser?

[richard coleman]

Mark,

I can concur (in Kubuntu 18.04).  It has happened on occasion in FireFox
(both current and ESR), Chrome, Chromium, Vivaldi (yea those last three are
basically the same thing, I know ;) ).  That's why I have a separate
install of Chromium that is just used for pgAdmin4.  So when the browser
crashes (for whatever reason) it doesn't take down pgAdmin and when pgAdmin
goes pear shaped, it doesn't take everything *else* down.

rik.

On Fri, Aug 2, 2019 at 3:38 PM Mark Murawski 
wrote:

> Hey Avin,
>
> I am using process isolation, but the issue is that the main
> chrome/firefox stops behaving normally.  And it's not just on my pc.
> It's like the network stack crashes inside the browser or locks up or
> something like that.
>
> I'll run into a situation where pages just no longer load.  I can select
> an existing tab and scroll around, and click on things and sometimes the
> tab still works, sometimes it doesn't.  Closing that tab and opening a
> new one and then entering a new url will just result in a blank page and
> nothing loads.
>
> Restarting the browser solves the issue.
>
> It's fairly rare these days, but sometimes the entire browser just
> 'breaks'.
>
>
>
> On 7/29/19 11:02 PM, Avin Kavish wrote:
> > Hey Mark,
> >
> > I find this hard to believe as chrome uses process isolation per site
> >  by
> > default. I believe firefox does too
> > <
> https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Multiprocess_Firefox>.
>
> > Whenever a website crashes only that tab crashes. It will prompt you to
> > recover or kill that tab in isolation. I'm a web developer too and I
> > sometimes let infinite recursion get through in my apps but I usually
> > end up being able to kill the tab without affecting the rest of my work.
> > Maybe the setting is turned off on your pc, you can check here,
> > chrome://flags/#site-isolation-trial-opt-out
> >
> > Regards,
> > Avin
> >
>
>
>

Re: no results in 4.11 Ubuntu

[richard coleman]

Richard,

As far as I know, yea, though you can use your GMail or Outlook accounts as
well, if you have one.

rik.

On Thu, Aug 1, 2019 at 9:31 AM Richard Greenwood <
richard.greenw...@gmail.com> wrote:

> Thanks for the info. Do I really have to create an account just to view
> the issue? The link you sent just goes to a postgresql.org "sign in" page.
>
> On Thu, Aug 1, 2019 at 6:58 AM richard coleman <
> rcoleman.ascen...@gmail.com> wrote:
>
>> Richard,
>>
>> Congratulations, you too have been hit by the mis-packaged pgAdmin4.11
>> bug recorded as Issue # 4520
>> <https://redmine.postgresql.org/issues/4520#change-17568> (among others)
>> .
>>
>> *TLDR* version; pgAdmin 4.11 is dependent on a version of psycopg2 that
>> isn't in the repository (any repository) and wasn't included in the
>> pgAdmin4 installer package for Linux versions.  There is a workaround
>> listed in that bug report of side loading the library and manually tweaking
>> some paths.
>>
>> They are aware of the issue, and someone(s) is/are working on it.  I hope
>> it's resolved soon (I've been bitten by the same issue).
>>
>> So patience, hope, and try the workaround if you're comfortable with that
>> sort of thing.
>>
>> Good luck,
>>
>> rik.
>>
>> On Thu, Aug 1, 2019 at 8:52 AM Richard Greenwood <
>> richard.greenw...@gmail.com> wrote:
>>
>>> I'm not getting any results from any query in pgAdmin 4.11 on Ubuntu. I
>>> only get a message:
>>>
>>> 'table_oid'
>>>
>>> I've tried on two Ubuntu 18.04 based computers (XUbuntu and Mint) in
>>> Firefox and Chrome against 3 servers. Queries in pgAdminIII and psql are
>>> fine. My "about" info below:
>>>
>>>
>>> Version
>>> 4.11
>>> Copyright
>>> Copyright (C) 2013 - 2019, The pgAdmin Development Team
>>> Python Version
>>> 3.6.8 (default, Jan 14 2019, 11:02:34) [GCC 8.0.1 20180414
>>> (experimental) [trunk revision 259383]]
>>> Flask Version
>>> 0.12.2
>>> Application Mode
>>> Desktop
>>> Current User
>>> pgadm...@pgadmin.org
>>>
>>>
>>>
>>>
>>> --
>>> Richard W. Greenwood, PLS
>>> www.greenwoodmap.com
>>>
>>
>
> --
> Richard W. Greenwood, PLS
> www.greenwoodmap.com
>

Re: no results in 4.11 Ubuntu

[richard coleman]

Richard,

Congratulations, you too have been hit by the mis-packaged pgAdmin4.11 bug
recorded as Issue # 4520
 (among others) .

*TLDR* version; pgAdmin 4.11 is dependent on a version of psycopg2 that
isn't in the repository (any repository) and wasn't included in the
pgAdmin4 installer package for Linux versions.  There is a workaround
listed in that bug report of side loading the library and manually tweaking
some paths.

They are aware of the issue, and someone(s) is/are working on it.  I hope
it's resolved soon (I've been bitten by the same issue).

So patience, hope, and try the workaround if you're comfortable with that
sort of thing.

Good luck,

rik.

On Thu, Aug 1, 2019 at 8:52 AM Richard Greenwood <
richard.greenw...@gmail.com> wrote:

> I'm not getting any results from any query in pgAdmin 4.11 on Ubuntu. I
> only get a message:
>
> 'table_oid'
>
> I've tried on two Ubuntu 18.04 based computers (XUbuntu and Mint) in
> Firefox and Chrome against 3 servers. Queries in pgAdminIII and psql are
> fine. My "about" info below:
>
>
> Version
> 4.11
> Copyright
> Copyright (C) 2013 - 2019, The pgAdmin Development Team
> Python Version
> 3.6.8 (default, Jan 14 2019, 11:02:34) [GCC 8.0.1 20180414 (experimental)
> [trunk revision 259383]]
> Flask Version
> 0.12.2
> Application Mode
> Desktop
> Current User
> pgadm...@pgadmin.org
>
>
>
>
> --
> Richard W. Greenwood, PLS
> www.greenwoodmap.com
>

Re: pgadmin4 - Use classic style interface, don't launch browser?

[richard coleman]

Avin,

Visual Studio Code (VSC) [a very nice if somewhat heavy weight editor] is
written in part using the Electron Framework {
https://en.wikipedia.org/wiki/Visual_Studio_Code} so it's using Node.js and
the Blink rendering engine as well as C++ and C#.  It's *not* using Atom,
nor can it be considered a browser by any definition.  VSC is a traditional
desktop application complete with it's own UI aimed squarely at the
desktop.  When you close it, you are stopping the application.  If you open
multiple windows, you are running multiple instances.  It's just makes use
of traditional web technologies in its development.

Just thought I would clear that up,

rik.

On Tue, Jul 30, 2019 at 10:37 PM Avin Kavish  wrote:

> On the topic of speed, the current limitation is not imposed by the fact
> that it is run inside the browser, fyi some really popular and successful
> apps are web based, even visual studio code. It's more of an architectural
> and design problem than a platform issue.
>
I'm not very familiar with the code yet, but I suspect the following could
> be factors,
>
>- a lack of caching on both the client and the server,
>- excessive amounts of DOM nodes (currently around 4000 at idle),
>- excessive nesting using tables,
>- lack of a view reconciliation library such as React/Angular
>- usage of AMD modules making dead-code elimination (tree-shaking)
>impossible, if asynchronous loading was the intention, webpack supports
>dynamic imports with ESModules while retaining the benefits of 
> tree-shaking.
>- lack of skeleton uis that are perceived as being faster - most top
>sites do this now making them look faster even if the time to interactive
>is the same
>- waiting on ajax requests before loading UIs, (theory) (the query
>tool takes 2-3s to open, is this why?)
>
> There's more to discover, I'm still reading through.
>
> Modern UI design philosophy is to react immediately to user response by
> showing something as close to the real interface as possible and then to
> load the data asynchronously behind a loading indicator, which is done in
> some situations but often not convincing enough or not immediate enough.
> (again, query tool, anywhere between 2-4s till first paint) Anywhere over
> one second and frustration sets in. 100ms should be the target to keep
> power users happy.
>
> More info:
> Performance:
> https://developers.google.com/web/fundamentals/performance/rail
> DOM Size:
> https://developers.google.com/web/tools/lighthouse/audits/dom-size
>
> The best way to identify areas that require improvement is to run the
> lighthouse
> <https://chrome.google.com/webstore/detail/lighthouse/blipmdconlkpinefehnmjammfjpmpbjk>
> auditing tool.
>
>
> On Tue, Jul 30, 2019 at 5:46 PM richard coleman <
> rcoleman.ascen...@gmail.com> wrote:
>
>> Dave,
>>
>> That's true.  Of course that's the ultimate draw back of the
>> client/server model.  Having *just* a server isn't enough, you need a
>> *client* as well.  pgAdmin4 is *just* the server portion of that model.
>> It's relying on *borrowing* someone else's client.  That's frees up
>> quite a bit of resources, not having to write an actual client.
>> Unfortunately that means you have to deal with all of the limitations;
>> speed, footprint, compatibility, security, capabilities that that entails.
>> Contrary to the thought in some circles, not *everything* is amenable to
>> being served through a web browser.
>>
>> just one man's opinion.
>>
>> On Tue, Jul 30, 2019 at 4:10 AM Dave Page  wrote:
>>
>>>
>>>
>>> On Mon, Jul 29, 2019 at 7:31 PM Mark Murawski <
>>> markm-li...@intellasoft.net> wrote:
>>>
>>>>
>>>> Would there be a possibility of embedding chromium?  Since of course
>>>> it's actively developed and everyone including their pet cat are using
>>>> it as a rendering engine these days (including microsoft)  Not sure of
>>>> the compatibility with the BSD license would go...
>>>>
>>>
>>> It's technically possible of course (one most, but not all of our
>>> supported platforms), but would be a massive amount of work, probably tying
>>> up most of my team for months whilst they figure out how to glue all the
>>> pieces together into Qt on Windows, Mac and Linux. I'd far rather they were
>>> building actual features.
>>>
>>> --
>>> Dave Page
>>> Blog: http://pgsnake.blogspot.com
>>> Twitter: @pgsnake
>>>
>>> EnterpriseDB UK: http://www.enterprisedb.com
>>> The Enterprise PostgreSQL Company
>>>
>>

Re: Appreciation for pgAdmin 4's progress

[richard coleman]

I concur.  Ctrl-C/Ctrl-V is basically muscle memory at this point.
Unfortunately though there are times when it's particularly jarring.
Selecting things are done in pgAdmin4 with the mouse/track ball/etc. so
your hand is already off the keyboard.  So for example; you select an sql
statement to copy/paste/make a small change/run a process I do all the time
in pgAdmin4.  Select->right-click->grumble about *useless
options*->Ctrl-C->move
to another area with mouse->Ctrl-V.

It seems especially strange since if you select a cell in the results pane
the copy / paste options are in *that* context menu.

Question:  Why would a*nyone* ever want to 'Remove Panel', 'Detach Panel',
or 'Add Panel' (the only options in the current query tool context menu)?

   - You can't move them outside of the tab and only within a of a smallish
   portion of the current tab.
   - You can't reattach them, so trying to use that option to rearrange
   them doesn't work.
   - The only way to *fix* it, if you've accidentally selected it is
the *nuclear
   *option of 'Reset Layout'.

There are just certain items that people *expect* in a context menu,
especially one that's associated with a text editor.  *None* of them
currently exist in the context menu of the query tool.  It would be *nice* if
that could be addressed, sooner as opposed to later.

Thanks,

rik.


On Tue, Jul 30, 2019 at 12:26 PM Dave Caughey  wrote:

> Correct.  But the absence of support in the context menu is a basic UI
> usability issue. Instead we only have "remove panel", "detach panel", "add
> panel".
>
> Context menus are an essential usability feature.  A context menu is
> intended to allow the user to quickly access the basic operations that
> apply to whatever is clicked on / selected (i.e., the "context"), and the
> menu items should be biased towards very commonly used actions (e.g., e.g.,
> copy/paste, new, etc.).  The most frequently used should be situated near
> the top of the context menu to minimize the mouse movement required to get
> to the desired operation. Less frequently-used stuff should be buried in
> submenus because the usability hit required to get to these uncommon
> operations is a big deal, compared with making it easier to get to the
> common operations.
>
> I totally understand that you don't think it's a big issue because
> (clearly) you're happy to use keyboard shortcuts.  But that's that way you
> prefer to work.   But many (most?) people rely on context menus, and it's
> just an unnecessary usability irritant when the stuff that you expect to
> find in a context menu is missing (e.g., #4229) or when the context menu
> hasn't had any thought given to the relative frequency of the operations
> (e.g., right-click on a table in the navigation pane, and you'll see
> less-frequently used operations like "Reset Statistics", "Drop Cascaded",
> "Maintenance", all above the super-common operations that are buried under
> "View/Edit Data..." way down at the bottom of the context menu.  I.e., the
> table context menu is just about as far from optimal as possible!)
>
> Is the absence/presence and thoughtful layout of context items a major
> functionality gap?  No.  But is it a *completely unnecessary* every-day
> usability irritant?  Yes.
>
> Cheers,
> Dave
>
>
>
> On Tue, Jul 30, 2019 at 11:52 AM Dave Page  wrote:
>
>>
>>
>> On Tue, Jul 30, 2019 at 4:45 PM Dave Caughey  wrote:
>>
>>> No, it doesn't work.  It's logged as #4229.   It would be *really* nice
>>> if this were fixed.
>>>
>>
>> 4229 is about adding a context menu for it. It works without though -
>> just use Ctrl/Cmd+C and Ctrl/Cmd+V. You can copy query text, cell values,
>> entire rows, or sets of rows.
>>
>> --
>> Dave Page
>> Blog: http://pgsnake.blogspot.com
>> Twitter: @pgsnake
>>
>> EnterpriseDB UK: http://www.enterprisedb.com
>> The Enterprise PostgreSQL Company
>>
>

Re: pgadmin4 - Use classic style interface, don't launch browser?

[richard coleman]

Dave,

That's true.  Of course that's the ultimate draw back of the client/server
model.  Having *just* a server isn't enough, you need a *client* as well.
pgAdmin4 is *just* the server portion of that model.  It's relying on
*borrowing* someone else's client.  That's frees up quite a bit of
resources, not having to write an actual client.  Unfortunately that means
you have to deal with all of the limitations; speed, footprint,
compatibility, security, capabilities that that entails.  Contrary to the
thought in some circles, not *everything* is amenable to being served
through a web browser.

just one man's opinion.

On Tue, Jul 30, 2019 at 4:10 AM Dave Page  wrote:

>
>
> On Mon, Jul 29, 2019 at 7:31 PM Mark Murawski 
> wrote:
>
>>
>> Would there be a possibility of embedding chromium?  Since of course
>> it's actively developed and everyone including their pet cat are using
>> it as a rendering engine these days (including microsoft)  Not sure of
>> the compatibility with the BSD license would go...
>>
>
> It's technically possible of course (one most, but not all of our
> supported platforms), but would be a massive amount of work, probably tying
> up most of my team for months whilst they figure out how to glue all the
> pieces together into Qt on Windows, Mac and Linux. I'd far rather they were
> building actual features.
>
> --
> Dave Page
> Blog: http://pgsnake.blogspot.com
> Twitter: @pgsnake
>
> EnterpriseDB UK: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>

Re: (Repeat.) Please give pgAdmin 4 its own GUI. The constant password inputs are driving me insane...

[richard coleman]

Dave,

Ah, I guess the two of us have a different understanding of *desktop* mode.
In your, and apparently pgAdmin4's case, it's a locally running web server
with a couple of settings tweaked.  In my, and perhaps many other people's,
understanding *desktop* mode is a program that you install on your machine
that contains it's own UI and *isn't* a server (even one that's running on
your local machine) that you access with your web browser as you would
google.com or facebook.com.  Desktop mode is like pgAdmin3, non-desktop
(server) mode is like running apache locally that has had phpPgAdmin
installed.  In pgAdmin4's case it's using python not php and the
application and web server come as a bundle.

But thanks for pointing me to that web page.

rik.





On Mon, Jul 29, 2019 at 8:14 AM Dave Page  wrote:

> Hi
>
> On Mon, Jul 29, 2019 at 12:58 PM richard coleman <
> rcoleman.ascen...@gmail.com> wrote:
>
>> Dave,
>>
>> Thanks for helping to clear that up, I am sorry I misunderstood
>> Khushboo's response.  As for running in *desktop mode*, I didn't think
>> that was possible for quite some time.  I sure haven't been able to find
>> out how to pull that off.  If you could explain, I would imagine I am not
>> the only one who would like that opportunity.
>>
>
> You are running in desktop mode, otherwise you would see the login page
> when you first connect (and you wouldn't get the master password prompt).
> See https://www.pgadmin.org/docs/pgadmin4/4.11/getting_started.html (and
> the relevant child pages on Server and Desktop deployment)
>
> Desktop vs. Server mode is not about the whether you access pgAdmin
> through a browser or not, but whether it's configured for running on a
> single user's desktop or on a web server that may be accessible to multiple
> users (or people who should not be using it at all; e.g. other people on
> the same LAN)
>
>
>>
>> rik.
>>
>> On Mon, Jul 29, 2019 at 4:45 AM Dave Page  wrote:
>>
>>> Hi
>>>
>>> On Sat, Jul 27, 2019 at 8:50 PM richard coleman <
>>> rcoleman.ascen...@gmail.com> wrote:
>>>
>>>> (sorry about the last missive - continued)
>>>>
>>>> On Sat, Jul 27, 2019 at 3:38 PM richard coleman <
>>>> rcoleman.ascen...@gmail.com> wrote:
>>>>
>>>>> Darren,
>>>>>
>>>>> On Sat, Jul 27, 2019 at 3:03 PM Darren Duncan 
>>>>> wrote:
>>>>>
>>>>>> Have you tried using more than one browser?
>>>>>> that's what I've taken to doing, I have a separate install of
>>>>>> Chromium just for pgAdmin4.  I've even changed the browser command to
>>>>>
>>>>>  "chromium-browser %URL% " so that it starts with the right browser.
>>>>
>>>> Although not all browsers are apparently equal.  Back on 2019-06-19
>>>> 04:10:13 Khushboo Vashi 
>>>> wrote in response to an issue I was having under Chromium;
>>>>
>>>>> "I would suggest, try a different browser as well as Chromium is not
>>>>> the
>>>>> supported browser for pgAdmin."
>>>>
>>>> Which suggests that there is *a supported browser* for pgAdmin4.  This
>>>> begs the question, if there's only a *single* supported browser, what
>>>> exactly is the point of a web app?  It's like web sites that only worked
>>>> correctly under IE6.
>>>>
>>>
>>> Don't mistake the phrasing there as an implication that there's only a
>>> single supported browser. Khushboo's first language is not English.
>>>
>>> We (the team at EDB, I can't speak for others) test on Chrome, Firefox,
>>> Safari, IE and Edge. For anyone using other browsers, the first step for us
>>> in diagnosing an issue is going to be to try to reproduce it on one of the
>>> browsers we test with. It's not feasible for us to test with everything
>>> that is out there.
>>>
>>>
>>>>
>>>> Developing pgAdmin4 as a *web app*/*web server* thing might make sense
>>>> from a development standpoint, but personally I think it introduces way
>>>> more problems than it solves.
>>>>
>>>
>>> It certainly does cause some problems that we didn't have before, but
>>> it's proven itself to solve a lot more.
>>>
>>> There's also the fact that running over the web is exactly what many
>>> people want these days. I would guesstimate that we probably see something
>>> like 50% of users we interact with running in web mode, and 50% in desktop
>>> mode. Download-wise, the number of container pulls is far outstripping the
>>> number of other downloads these days with Docker hub reporting > 10
>>> million. All of those users are running in web mode as that's the only way
>>> the container runs, so it's clear that the web app architecture is the
>>> right thing for a significant number of users.
>>>
>>> --
>>> Dave Page
>>> Blog: http://pgsnake.blogspot.com
>>> Twitter: @pgsnake
>>>
>>> EnterpriseDB UK: http://www.enterprisedb.com
>>> The Enterprise PostgreSQL Company
>>>
>>
>
> --
> Dave Page
> Blog: http://pgsnake.blogspot.com
> Twitter: @pgsnake
>
> EnterpriseDB UK: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>

Re: (Repeat.) Please give pgAdmin 4 its own GUI. The constant password inputs are driving me insane...

[richard coleman]

Dave,

Thanks for helping to clear that up, I am sorry I misunderstood Khushboo's
response.  As for running in *desktop mode*, I didn't think that was
possible for quite some time.  I sure haven't been able to find out how to
pull that off.  If you could explain, I would imagine I am not the only one
who would like that opportunity.

rik.

On Mon, Jul 29, 2019 at 4:45 AM Dave Page  wrote:

> Hi
>
> On Sat, Jul 27, 2019 at 8:50 PM richard coleman <
> rcoleman.ascen...@gmail.com> wrote:
>
>> (sorry about the last missive - continued)
>>
>> On Sat, Jul 27, 2019 at 3:38 PM richard coleman <
>> rcoleman.ascen...@gmail.com> wrote:
>>
>>> Darren,
>>>
>>> On Sat, Jul 27, 2019 at 3:03 PM Darren Duncan 
>>> wrote:
>>>
>>>> Have you tried using more than one browser?
>>>> that's what I've taken to doing, I have a separate install of Chromium
>>>> just for pgAdmin4.  I've even changed the browser command to
>>>
>>>  "chromium-browser %URL% " so that it starts with the right browser.
>>
>> Although not all browsers are apparently equal.  Back on 2019-06-19
>> 04:10:13 Khushboo Vashi 
>> wrote in response to an issue I was having under Chromium;
>>
>>> "I would suggest, try a different browser as well as Chromium is not the
>>> supported browser for pgAdmin."
>>
>> Which suggests that there is *a supported browser* for pgAdmin4.  This
>> begs the question, if there's only a *single* supported browser, what
>> exactly is the point of a web app?  It's like web sites that only worked
>> correctly under IE6.
>>
>
> Don't mistake the phrasing there as an implication that there's only a
> single supported browser. Khushboo's first language is not English.
>
> We (the team at EDB, I can't speak for others) test on Chrome, Firefox,
> Safari, IE and Edge. For anyone using other browsers, the first step for us
> in diagnosing an issue is going to be to try to reproduce it on one of the
> browsers we test with. It's not feasible for us to test with everything
> that is out there.
>
>
>>
>> Developing pgAdmin4 as a *web app*/*web server* thing might make sense
>> from a development standpoint, but personally I think it introduces way
>> more problems than it solves.
>>
>
> It certainly does cause some problems that we didn't have before, but it's
> proven itself to solve a lot more.
>
> There's also the fact that running over the web is exactly what many
> people want these days. I would guesstimate that we probably see something
> like 50% of users we interact with running in web mode, and 50% in desktop
> mode. Download-wise, the number of container pulls is far outstripping the
> number of other downloads these days with Docker hub reporting > 10
> million. All of those users are running in web mode as that's the only way
> the container runs, so it's clear that the web app architecture is the
> right thing for a significant number of users.
>
> --
> Dave Page
> Blog: http://pgsnake.blogspot.com
> Twitter: @pgsnake
>
> EnterpriseDB UK: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>

Re: pgadmin4 - Use classic style interface, don't launch browser?

[richard coleman]

y', createWindow)
>
> app.on('window-all-closed', () => {
>   if (process.platform !== 'darwin') {
> app.quit()
>   }
> })
>
> app.on('activate', () => {
>   if (win === null) {
> createWindow()
>   }
> })
>
> That's all there is to it. Once you have that working, you can take it a
> step further by getting electron to launch the pgadmin4 server if it is not
> running already by using spawn
> <https://nodejs.org/api/child_process.html#child_process_child_process_execsync_command_options>
>
> It's nice that you included the above, but it's not terribly helpful to
> the *non*-programmer.  I could write the Lorentz transformation equations
> to handle relative velocities in special relativity
>
[image: image.png]

but unless you're familiar with differential calculus and special
relativity it's not very helpful.


> *Maybe an alternate launch option based on Electron should be an
> officially supported feature ?*
>
Maybe.  Though I think it would have to handle the above mentioned
limitations, and be *built in* for it to help *most* people.

So there, no attacks, insults, or other *negativity. * Just one man's
opinion.

>
>
> On Sun, Jul 28, 2019 at 1:07 AM richard coleman <
> rcoleman.ascen...@gmail.com> wrote:
>
>> Hi Avin,
>>
>> My $0.02
>>
>> On Sat, Jul 27, 2019 at 2:11 PM Avin Kavish  wrote:
>>
>>> Hey,
>>>
>>> Here's some unofficial input on the topic.
>>>
>>> This request baffles me for two reasons.
>>>
>>> a. Why does one need a standalone window when they can have pgAdmin open
>>> in a tab while multi-tasking. Is there ever a time when the web browser is
>>> closed while using a pc in 2019? If you lose tabs you can pin the tab and
>>> it will always be on the left side.
>>>
>> quite often actually.  I have *lots* of work to do that doesn't involve
>> a web browser.
>>
>>
>>> b. If you want it to run in it's own window, you can drag and pull the
>>> tab to it's own standalone window.
>>>
>> pulling the tab out wouldn't do *anything* toward solving his problem,
>> which revolved around password management
>>
>>> If that doesn't solve your problem,
>>>
>>> You can try Nativefier but you might need to launch pgAdmin on the same
>>> port each time. It basically wraps any web site in an electron app.
>>> Electron fyi allows developing desktop apps using web technologies. It's
>>> based on chromium and nodejs and renders web apps just like google chrome
>>> would. https://github.com/jiahaog/nativefier
>>>
>>  so he would need to install nodejs, npm, nativefier, either open a
>> command line/terminal every time he wants to start pgAdmin4 or write a
>> batch/shell script to start it.  He would also have to remember to start
>> the pgAdmin *server* separately and forget about using the "New pgAdmin
>> window" function.  To add insult to injury, he'd have to have
>> separate scripts/commands if he should want a tray icon or to run it full
>> screen.
>>
>>>
>>> Or if you are a javascript developer you can write an electron app
>>> yourself to encapsulate and extend upon the current functionality.
>>> https://electronjs.org/
>>>
>> so, your final suggestion is that, *if* he's a javascript developer he
>> could simply *write his own program* to fix a perceived pgAdmin4
>> shortcoming.
>>
>>> Personally, I find it convenient to have it as a tab while reading docs
>>> and other stuff and often prefer it to switching to my IDE.
>>>
>>> I'm glad that you find the current set up convenient, unfortunately it
>> seems like this is a problem for at least Mark and tutiluren.
>>
>>> Once again, this is unofficial. I'm not part of the team.
>>>
>> neither am I.
>>
>> Personally I have my own issues with the decision to write pgAdmin4 as a *web
>> app* running in it's own self contained web server.  However I don't
>> think that there is much of a desire among the *official* dev team to
>> change this.
>>
>> rik.
>>
>>> Regards,
>>> Avin
>>>
>>> On Sat, Jul 27, 2019 at 10:51 PM Murtuza Zabuawala <
>>> murtuza.zabuaw...@enterprisedb.com> wrote:
>>>
>>>> Hello,
>>>>
>>>> I am afraid this is not possible at a moment,  pgAdmin4 doesn't have
>>>> its own UI  rendering engine so it is dependent on the default web browser
>>>> on the user's system.
>>>>
>>>> -- Murtuza
>>>>
>>>> On Fri, 26 Jul 2019, 21:32 Mark Murawski, 
>>>> wrote:
>>>>
>>>>> Hello!
>>>>>
>>>>> How can I go back to the traditional pgadmin4 interface where it runs
>>>>> in
>>>>> its own window.  I do not want to launch it as a browser tab.
>>>>>
>>>>>
>>>>>

Re: pgAdmin4 (v 4.11) SELECT * returns 'table_oid'

[richard coleman]

I think I have been bit by Bug #4520
<https://redmine.postgresql.org/issues/4520?issue_count=196&issue_position=3&next_issue_id=4519&prev_issue_id=4525>.
I hope there is a solution soon.

rik.

On Sat, Jul 27, 2019 at 4:14 PM richard coleman 
wrote:

> 'ello all,
>
> When running the following query:
>
> SELECT * FROM live.tbl_documents limit 1;
>
> in pgAdmin4 it returns *no* output and switches to the Messages tab with
> the following message:
>
> 'table_oid'
>
>
> The same query against the same table in the same database run at the psql
> prompt returns the records as expected.
>
> postgreSQL 10.3
>
> using pgAdmin4
> Version
> 4.11
> Copyright
> Copyright (C) 2013 - 2019, The pgAdmin Development Team
> Python Version
> 3.6.8 (default, Jan 14 2019, 11:02:34) [GCC 8.0.1 20180414 (experimental)
> [trunk revision 259383]]
> Flask Version
> 0.12.2
> Application Mode
> Desktop
> Current User
> pgadm...@pgadmin.org
>
> Running on Chromium
> Version 75.0.3770.90 (Official Build) Built on Ubuntu , running on Ubuntu
> 18.04 (64-bit)
>
> Kubuntu 18.04.
>
> Table:
> CREATE TABLE live.tbl_documents
> (
> id character varying(50) COLLATE pg_catalog."default" NOT NULL,
> company_no character varying(32) COLLATE pg_catalog."default",
> tariff_id integer,
> scac character(4) COLLATE pg_catalog."default",
> type character varying(50) COLLATE pg_catalog."default" NOT NULL,
> name character varying(200) COLLATE pg_catalog."default" NOT NULL,
> filelocation character varying(200) COLLATE pg_catalog."default" NOT
> NULL,
> description character varying(200) COLLATE pg_catalog."default" NOT
> NULL,
> archive boolean NOT NULL DEFAULT false,
> par_id character varying(50) COLLATE pg_catalog."default",
> category character varying(250) COLLATE pg_catalog."default",
> visible_in_vision boolean NOT NULL DEFAULT false,
> tariffrequest_id character varying(50) COLLATE pg_catalog."default",
> entered_on timestamp without time zone NOT NULL DEFAULT now(),
> invoice_id character varying(40) COLLATE pg_catalog."default",
> lastwritetime timestamp without time zone,
> shipment_id character varying(40) COLLATE pg_catalog."default",
> CONSTRAINT tbl_documents_pkey PRIMARY KEY (id),
> CONSTRAINT tbl_documents_par_id_fkey FOREIGN KEY (par_id)
> REFERENCES live.tbl_pars (par_id) MATCH SIMPLE
> ON UPDATE NO ACTION
> ON DELETE NO ACTION
> )
> WITH (
> OIDS = FALSE
> )
> TABLESPACE pg_default;
>
>

pgAdmin4 (v 4.11) SELECT * returns 'table_oid'

[richard coleman]

'ello all,

When running the following query:

SELECT * FROM live.tbl_documents limit 1;

in pgAdmin4 it returns *no* output and switches to the Messages tab with
the following message:

'table_oid'


The same query against the same table in the same database run at the psql
prompt returns the records as expected.

postgreSQL 10.3

using pgAdmin4
Version
4.11
Copyright
Copyright (C) 2013 - 2019, The pgAdmin Development Team
Python Version
3.6.8 (default, Jan 14 2019, 11:02:34) [GCC 8.0.1 20180414 (experimental)
[trunk revision 259383]]
Flask Version
0.12.2
Application Mode
Desktop
Current User
pgadm...@pgadmin.org

Running on Chromium
Version 75.0.3770.90 (Official Build) Built on Ubuntu , running on Ubuntu
18.04 (64-bit)

Kubuntu 18.04.

Table:
CREATE TABLE live.tbl_documents
(
id character varying(50) COLLATE pg_catalog."default" NOT NULL,
company_no character varying(32) COLLATE pg_catalog."default",
tariff_id integer,
scac character(4) COLLATE pg_catalog."default",
type character varying(50) COLLATE pg_catalog."default" NOT NULL,
name character varying(200) COLLATE pg_catalog."default" NOT NULL,
filelocation character varying(200) COLLATE pg_catalog."default" NOT
NULL,
description character varying(200) COLLATE pg_catalog."default" NOT
NULL,
archive boolean NOT NULL DEFAULT false,
par_id character varying(50) COLLATE pg_catalog."default",
category character varying(250) COLLATE pg_catalog."default",
visible_in_vision boolean NOT NULL DEFAULT false,
tariffrequest_id character varying(50) COLLATE pg_catalog."default",
entered_on timestamp without time zone NOT NULL DEFAULT now(),
invoice_id character varying(40) COLLATE pg_catalog."default",
lastwritetime timestamp without time zone,
shipment_id character varying(40) COLLATE pg_catalog."default",
CONSTRAINT tbl_documents_pkey PRIMARY KEY (id),
CONSTRAINT tbl_documents_par_id_fkey FOREIGN KEY (par_id)
REFERENCES live.tbl_pars (par_id) MATCH SIMPLE
ON UPDATE NO ACTION
ON DELETE NO ACTION
)
WITH (
OIDS = FALSE
)
TABLESPACE pg_default;

Re: (Repeat.) Please give pgAdmin 4 its own GUI. The constant password inputs are driving me insane...

[richard coleman]

(sorry about the last missive - continued)

On Sat, Jul 27, 2019 at 3:38 PM richard coleman 
wrote:

> Darren,
>
> On Sat, Jul 27, 2019 at 3:03 PM Darren Duncan 
> wrote:
>
>> Have you tried using more than one browser?
>> that's what I've taken to doing, I have a separate install of Chromium
>> just for pgAdmin4.  I've even changed the browser command to
>
>  "chromium-browser %URL% " so that it starts with the right browser.

Although not all browsers are apparently equal.  Back on 2019-06-19
04:10:13 Khushboo Vashi  wrote
in response to an issue I was having under Chromium;

> "I would suggest, try a different browser as well as Chromium is not the
> supported browser for pgAdmin."

Which suggests that there is *a supported browser* for pgAdmin4.  This begs
the question, if there's only a *single* supported browser, what exactly is
the point of a web app?  It's like web sites that only worked
correctly under IE6.

Developing pgAdmin4 as a *web app*/*web server* thing might make sense from
a development standpoint, but personally I think it introduces way more
problems than it solves.

just my $0.02.


> Load pgAdmin and/or a small number of secured things you want to stay
>> logged in
>> for longer periods, while do your majority of activities or the ones
>> you'd want
>> to clear your browser for in others.
>>
>> I for example have Safari plus Firefox plus Chrome and compartmentalize
>> my
>> activity between them, and they're all mutually isolated.
>>
>> -- Darren Duncan
>>
>> On 2019-07-27 5:54 a.m., tutilu...@tutanota.com wrote:
>> > Sorry for repeating this, but the only replies I got were unrelated to
>> what I
>> > typed, instead briefly discussing master passwords.
>> >
>> > Every single day, even after getting rid of the "master password"
>> nonsense
>> > (which was a nightmare in itself), pgAdmin keeps asking me, again
>> and again,
>> > to enter the password when I try to connect to my servers. This is
>> cleared
>> > every single time I clear my browser data, which is an absolute
>> necessity
>> > multiple times a day.
>> >
>> > I don't want pgAdmin to have anything to do with my browser, and
>> dealing
>> > with multiple "profiles" is very impractical and tedious to set up.
>> I don't
>> > want them connected whatsoever. Please make a proper GUI that is
>> entirely
>> > separate from your "normal browser", allowing it to remember
>> passwords and
>> > not constantly forget them because it's attached to your normal
>> browser's data.
>> >
>> > The GUI can be an embedded browser and has no need whatsoever for
>> constant
>> > security updates because all it does is load pgAdmin 4's code. It
>> doesn't
>> > need to be able to do anything else, nor should it be able to. It
>> shouldn't
>> > even be apparent to the user that it's a browser at all -- it
>> should just
>> > open a GUI window with pgAdmin 4 inside of it -- not rely on my
>> browser
>> > environment.
>> >
>> > I almost recall that this actually was done in the past. Why you
>> would
>> > abandon this idea is inexplicable to me, since "just using the
>> normal
>> > browser" causes so many annoying problems.
>> >
>> >
>>
>>
>>
>>

Re: (Repeat.) Please give pgAdmin 4 its own GUI. The constant password inputs are driving me insane...

[richard coleman]

Darren,

On Sat, Jul 27, 2019 at 3:03 PM Darren Duncan 
wrote:

> Have you tried using more than one browser?
> that's what I've taken to doing, I have a separate install of Chromium
> just for pgAdmin4.  I've even changed the browser command to
> Load pgAdmin and/or a small number of secured things you want to stay
> logged in
> for longer periods, while do your majority of activities or the ones you'd
> want
> to clear your browser for in others.
>
> I for example have Safari plus Firefox plus Chrome and compartmentalize my
> activity between them, and they're all mutually isolated.
>
> -- Darren Duncan
>
> On 2019-07-27 5:54 a.m., tutilu...@tutanota.com wrote:
> > Sorry for repeating this, but the only replies I got were unrelated to
> what I
> > typed, instead briefly discussing master passwords.
> >
> > Every single day, even after getting rid of the "master password"
> nonsense
> > (which was a nightmare in itself), pgAdmin keeps asking me, again
> and again,
> > to enter the password when I try to connect to my servers. This is
> cleared
> > every single time I clear my browser data, which is an absolute
> necessity
> > multiple times a day.
> >
> > I don't want pgAdmin to have anything to do with my browser, and
> dealing
> > with multiple "profiles" is very impractical and tedious to set up.
> I don't
> > want them connected whatsoever. Please make a proper GUI that is
> entirely
> > separate from your "normal browser", allowing it to remember
> passwords and
> > not constantly forget them because it's attached to your normal
> browser's data.
> >
> > The GUI can be an embedded browser and has no need whatsoever for
> constant
> > security updates because all it does is load pgAdmin 4's code. It
> doesn't
> > need to be able to do anything else, nor should it be able to. It
> shouldn't
> > even be apparent to the user that it's a browser at all -- it should
> just
> > open a GUI window with pgAdmin 4 inside of it -- not rely on my
> browser
> > environment.
> >
> > I almost recall that this actually was done in the past. Why you
> would
> > abandon this idea is inexplicable to me, since "just using the normal
> > browser" causes so many annoying problems.
> >
> >
>
>
>
>

Re: pgadmin4 - Use classic style interface, don't launch browser?

[richard coleman]

Hi Avin,

My $0.02

On Sat, Jul 27, 2019 at 2:11 PM Avin Kavish  wrote:

> Hey,
>
> Here's some unofficial input on the topic.
>
> This request baffles me for two reasons.
>
> a. Why does one need a standalone window when they can have pgAdmin open
> in a tab while multi-tasking. Is there ever a time when the web browser is
> closed while using a pc in 2019? If you lose tabs you can pin the tab and
> it will always be on the left side.
>
quite often actually.  I have *lots* of work to do that doesn't involve a
web browser.


> b. If you want it to run in it's own window, you can drag and pull the tab
> to it's own standalone window.
>
pulling the tab out wouldn't do *anything* toward solving his problem,
which revolved around password management

> If that doesn't solve your problem,
>
> You can try Nativefier but you might need to launch pgAdmin on the same
> port each time. It basically wraps any web site in an electron app.
> Electron fyi allows developing desktop apps using web technologies. It's
> based on chromium and nodejs and renders web apps just like google chrome
> would. https://github.com/jiahaog/nativefier
>
 so he would need to install nodejs, npm, nativefier, either open a command
line/terminal every time he wants to start pgAdmin4 or write a batch/shell
script to start it.  He would also have to remember to start the pgAdmin
*server* separately and forget about using the "New pgAdmin window"
function.  To add insult to injury, he'd have to have
separate scripts/commands if he should want a tray icon or to run it full
screen.

>
> Or if you are a javascript developer you can write an electron app
> yourself to encapsulate and extend upon the current functionality.
> https://electronjs.org/
>
so, your final suggestion is that, *if* he's a javascript developer he
could simply *write his own program* to fix a perceived pgAdmin4
shortcoming.

> Personally, I find it convenient to have it as a tab while reading docs
> and other stuff and often prefer it to switching to my IDE.
>
> I'm glad that you find the current set up convenient, unfortunately it
seems like this is a problem for at least Mark and tutiluren.

> Once again, this is unofficial. I'm not part of the team.
>
neither am I.

Personally I have my own issues with the decision to write pgAdmin4 as a *web
app* running in it's own self contained web server.  However I don't think
that there is much of a desire among the *official* dev team to change this.


rik.

> Regards,
> Avin
>
> On Sat, Jul 27, 2019 at 10:51 PM Murtuza Zabuawala <
> murtuza.zabuaw...@enterprisedb.com> wrote:
>
>> Hello,
>>
>> I am afraid this is not possible at a moment,  pgAdmin4 doesn't have its
>> own UI  rendering engine so it is dependent on the default web browser on
>> the user's system.
>>
>> -- Murtuza
>>
>> On Fri, 26 Jul 2019, 21:32 Mark Murawski, 
>> wrote:
>>
>>> Hello!
>>>
>>> How can I go back to the traditional pgadmin4 interface where it runs in
>>> its own window.  I do not want to launch it as a browser tab.
>>>
>>>
>>>

Re: Please give pgAdmin 4 its own GUI. The constant password inputs are driving me insane...

[richard coleman]

Dave,

There is no attack of any kind in that post.  I am sympathizing with Avin.
While I agree that there are use cases where a *master password* feature
makes sense, I disagree that it is the *majority* of cases, or even
applicable to the *majority* of users.  Therefore I believe that it is
*implemented* poorly.  If history is any guide there will be plenty more
users stumbling across this list frustrated and just wanting to know how to
'get rid of' or simply 'turn it off'.

So where I wrote sympathy and solutions, you choose to see attacks.  I
think that says more about you than about myself.

If the pgAdmin developers want *nothing* but praise and the occasional
sterile bug report they should probably stop reading, or shut down this
list.  After all, a link to the redmine bug report page
<https://redmine.postgresql.org> would suffice for the latter.

Whether writing commercial or open source software, paid or volunteer, some
people are *not* going to agree with your choices or decisions (just as
Linus).  As long as we are criticizing the software and not the people
writing it, the software and all of us, end up better for it.

I hope you take the time to think about what I've written,

rik.




On Thu, Jul 25, 2019 at 8:49 AM Dave Page  wrote:

> Richard,
>
> On Thu, Jul 25, 2019 at 1:08 PM richard coleman <
> rcoleman.ascen...@gmail.com> wrote:
>
>> Avin,
>>
>> I agree, the master password *nonsense* was poorly implemented.  I too
>> wish the developers would rethink it.  Until then there is a way to disable
>> it by setting an option in a config file.  I can provide more details if
>> you would like (or you could look for other more expansive posts by myself
>> on this topic in the list archives).
>>
>
> You've made your feelings known many times now, and we're all well aware
> of them - just as you are aware that there are legitimate security concerns
> that caused it to be implemented (that were raised by end users), ones that
> arguably warrant a medium level CVSS vulnerability score
> (CVSS:3.0/AV:L/AC:H/PR:N/UI:R/S:C/C:H/I:N/A:N), and other concerns such as
> allowing a network administrator to enforce security policy that led to the
> design.
>
> Please refrain from any further remarks that disparage the work of people
> who - in many cases, voluntarily - spend hundreds or thousands of hours of
> their time developing software that you get to use freely. Constructive
> feedback and better yet ideas or code are welcome always, but repeated
> negativity that is borderline ad hominem is not.
>
> --
> Dave Page
> Blog: http://pgsnake.blogspot.com
> Twitter: @pgsnake
>
>

Re: Bug when a column is JSON?

[richard coleman]

Dave,

Sorry about the typo in the previous missive, it *should* have read;

We've just gotten the 4.*10* release in .deb format.  Will we have to wait
until 4.*12* or maybe 4.*14* until we will see 4.*11*?


Otherwise, what platforms *does* the pgAdmin developers release on?

Since it isn't apparently *all* of the platforms that pgAdmin4 is developed
for, shouldn't the pgAdmin4 developers do so?  If not, shouldn't the triage
be better, and the rapid release be slower?  As you are aware, there have
been several instances where a new version has *broken* important
functionality in pgAdmin4.  It doesn't do a large portion of the user base
any favors if the developers release a *fix* in the form of a new version a
couple of days latter only to leave entire platforms bereft of that
solution.

rik.

On Thu, Jul 25, 2019 at 8:14 AM Dave Page  wrote:

>
>
> On Thu, Jul 25, 2019 at 1:11 PM richard coleman <
> rcoleman.ascen...@gmail.com> wrote:
>
>> Fahar,
>>
>> We've *just* gotten the 4.*10* release in .deb format.  Will we have to
>> wait until 4.*11* or maybe 4.*13* until we will see 4.10?
>>
>
> Neither Fahar nor the rest of the pgAdmin developers have any part in the
> production of the Debian packages. That is handled by a separate team who
> produce all the Debian/Ubuntu packages on apt.postgresql.org.
>
> --
> Dave Page
> Blog: http://pgsnake.blogspot.com
> Twitter: @pgsnake
>
> EnterpriseDB UK: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>

Re: Bug when a column is JSON?

[richard coleman]

Fahar,

We've *just* gotten the 4.*10* release in .deb format.  Will we have to
wait until 4.*11* or maybe 4.*13* until we will see 4.10?

Thanks,

rik.

On Thu, Jul 25, 2019 at 5:37 AM Fahar Abbas 
wrote:

> Hi,
>
> This fix will be available in 4.11 release today.
>
> On Thu, Jul 25, 2019 at 2:21 PM Michael Monerau 
> wrote:
>
>> Hi,
>>
>> Just ran into this bug when trying to simply list the contents of a table:
>>
>> [image: image.png]
>>
>> And the DataOutput panel is blank.
>>
>> It definitely works on other tables, and the connection to the server is
>> ok (it correctly pulls out the 268 rows, and downloading the CSV works ok).
>>
>> The only difference I can see between this table and others is that it
>> has a "JSON" type column.
>>
>> Is this a known bug?
>>
>> Best,
>> Michael
>>
>
>
> --
> Fahar Abbas
> QMG
> EnterpriseDB Corporation
> Phone Office: +92-51-835-8874
> Phone Direct: +92-51-8466803
> Mobile: +92-333-5409707
> Skype ID: *live:fahar.abbas*
> Website: www.enterprisedb.com
>

Re: Please give pgAdmin 4 its own GUI. The constant password inputs are driving me insane...

[richard coleman]

Avin,

I agree, the master password *nonsense* was poorly implemented.  I too wish
the developers would rethink it.  Until then there is a way to disable it
by setting an option in a config file.  I can provide more details if you
would like (or you could look for other more expansive posts by myself on
this topic in the list archives).

pgAdmin4 *should *save your connection passwords in an internal database
(separate from the browser) there's a 'save password' option when you are
setting up a connection.  If *that* isn't working, you should submit a bug.

If you want to do away with the need for passwords, you can do that at the
postgreSQL level by either setting your database to trust the ip address
that you are connecting from (in the pg_hba.conf file), or connecting via
another means such as SSL.

I hope that helps,

rik.

On Thu, Jul 25, 2019 at 4:21 AM Avin Kavish  wrote:

> I'm curious to know where the need for the master password arose and
> whether it can be disabled or made optional. I don't believe it is needed
> for personal PCs, the OS login is enough protection.
>
> On Thu, Jul 25, 2019 at 1:07 PM  wrote:
>
>> Every single day, even after getting rid of the "master password"
>> nonsense (which was a nightmare in itself), pgAdmin keeps asking me, again
>> and again, to enter the password when I try to connect to my servers. This
>> is cleared every single time I clear my browser data, which is an absolute
>> necessity multiple times a day.
>>
>> I don't want pgAdmin to have anything to do with my browser, and dealing
>> with multiple "profiles" is very impractical and tedious to set up. I don't
>> want them connected whatsoever. Please make a proper GUI that is entirely
>> separate from your "normal browser", allowing it to remember passwords and
>> not constantly forget them because it's attached to your normal browser's
>> data.
>>
>> The GUI can be an embedded browser and has no need whatsoever for
>> constant security updates because all it does is load pgAdmin 4's code. It
>> doesn't need to be able to do anything else, nor should it be able to. It
>> shouldn't even be apparent to the user that it's a browser at all -- it
>> should just open a GUI window with pgAdmin 4 inside of it -- not rely on my
>> browser environment.
>>
>> I almost recall that this actually was done in the past. Why you would
>> abandon this idea is inexplicable to me, since "just using the normal
>> browser" causes so many annoying problems.
>>
>

Re: How do I remove this stupid "master password"?

[richard coleman]

tutiluren,

I feel your pain.  Here's the *short* answer I passed along to someone
else.  There's a *much* longer discussion between myself and the dev that
thought this was a good idea that I can share if you are ever interested.

rik.

---
Welcome to the nanny state that pgAdmin4 has become.

There is a way to disable this feature. You need to add this string to a
config.py, config_distro.py, or config_local.py;
MASTER_PASSWORD_REQUIRED=False

Other than config.py, the other files, may or may not exist, so you'll have
to create at least one of them, if you want to use it.

The help page is here:
https://www.pgadmin.org/docs/pgadmin4/dev/master_password.html

Here's another link were people are looking for how to disable it.
https://askubuntu.com/questions/1150778/pgadmin4-disable-master-password

If you've accidentally enabled it, it may scramble all of your saved
passwords, so you'll have to enter them again.  At least you won't have to
keep entering the MASTER PASSWORD though.

Good luck,


On Tue, Jul 9, 2019 at 1:21 PM  wrote:

> Not long ago, I updated pgAdmin 4 as I did every time a new version was
> available (because it wouldn't stop pestering me about it), even though
> this was a massive chore and not automated in any way. Anyway, with some
> recent version, it started popping up this obnoxious, pointless "master
> password" idiocy, every single time I tried to click or load anything. It
> just wouldn't shut up about it. I tried setting an empty password, but of
> course it wouldn't even accept that.
>
> Eventually, after wasting countless hours on trying to find out how to
> disable this unwanted "feature", realizing that there was no way to do so
> (the supposed instructions were incomplete/nonsensical), I was forced to
> downgrade to the last version. From that point on, I stopped running my
> script which checks for new versions of pgAdmin 4 and downloads them for me
> (to save some time and energy every time it wants to update).
>
> The other day, I decided that my pgAdmin is getting too old, and hopefully
> they will have removed this stupidity by now. Alas, I found that it was
> still there, but I think it looked different this time. I'm not sure.
> Either way, furious that it wouldn't go away (this kind of thing is just as
> bad as, if not *worse* than, ads), I made a single space the "master
> password".
>
> Now, I'm forced to waste my time, energy and focus every single time I
> need to admin my databases by needlessly inputting a single space and click
> a button before it lets me in. And no, it doesn't remember this because I
> clear all browser data many times a day (out of necessity). It really does
> "add up" and makes me despise the software and look at it at a chore rather
> than something useful. I thought it was already bad enough that it requires
> a browser and has a "warmup time" (the first time each time the computer
> boots)...
>
> How do I turn this off? How do I make it never appear ever again? How do I
> disable it? I have no idea who thought that this was a good idea, but I
> strongly suspect that nobody did, and it was just added to piss people off.
> I've dealt with enough "bizarre" decisions made by software authors to
> still believe that they don't know what they're doing. They know. If they
> use the software themselves, they know. This has literally *no* practical
> purpose that I can think of, and wasn't even explained. It just appeared
> randomly one day with an update. "Here's some random unwanted change for
> the worse. Deal with it, user." ... you'd almost think that Microsoft had a
> finger in the development of this program.
>
> If there is some sort of edge-case scenario where this actually makes
> sense (I cannot think of any, and I have excellent imagination...), why not
> make this OPTIONAL? Why put it there BY DEFAULT, and why FORCE us to pick a
> "master password" even if we have no need for it and it's nothing but
> unwanted stupidity that makes us hate the authors of the software and swear
> to never, ever donate or help out the project in any way? Why turn your
> users into enemies?
>
> PS: Man, I long back to the days when pgAdmin III still worked and was
> maintained. It got so bad in the end that I had to click away countless
> error boxes before I could do anything in it...
>
> PS 2: This stuff about requiring people to create an account and submit
> all our data to Google to send e-mails to this list is just insanity. What
> is wrong with you people?! You apparently have done anything to shield
> yourselves from people contacting you. This lengthy, 48-step process of
> actually getting to send this damn e-mail is incredibly tiresome and
> insulting...
>

Re: [EXTERNAL] - Re: How to close pgAdmin4

[richard coleman]

Michelle,

Right click the little picture of the elephant, the context menu should
include an entry "Shut down server", select that and you will *correctly* shut
down pgAdmin4.

[image: context_menu_pgAdmin4_taskbar.png]

Some of your confusion probably stems from the fact, that contrary to
appearances, pgAdmin4 is still *not* a *desktop application*.  It would
*really* be nice if we could get an actual desktop application, like
pgAdmin3 was, as opposed to the lobotomized web server that pgAdmin4 is.

¯\_(ツ)_/¯

rik.

On Thu, Jun 27, 2019 at 9:59 AM Michelle Schwan 
wrote:

> Could you show a screen shot of that?  I cannot find the option to exit.
>
>
>
> *From:* Michel Feinstein 
> *Sent:* Thursday, June 27, 2019 9:54 AM
> *To:* George Weaver 
> *Cc:* pgAdmin Support 
> *Subject:* [EXTERNAL] - Re: How to close pgAdmin4
>
>
>
> Look for it in the system tray bar, at the lower right corner of the
> screen, right click it and see the option to exit.
>
>
>
> On Thu, Jun 27, 2019, 10:42 George Weaver  wrote:
>
> Good morning,
>
> I would like to know how to "really" close pgAdmin4.
>
> When I close the pgAdmin4 tab or the browser supporting pgAdmin4
> (Firefox 67.0.4), this does not close pgAdmin4.  It still resides in
> Task Manager (Windows 10).
>
> This is very inconvenient.  If after closing pgAdmin4 I try and delete a
> database via other means (eg psql) I get the following error message:
>
>  DROP DATABASE IF EXISTS development;
>
>  ERROR:  database "development" is being accessed by other users
>  DETAIL:  There are 2 other sessions using the database.
>
> This forces me to start Task Manager, scroll down to pgAdmin4 and select
> End Task.
>
> How do I close pgAdmin4 so it is no longer running on the computer and I
> can avoid these nuisance steps.
>
> Thanks,
>
> George
>
>
>
>

Re: change connection in PgAdmin4

[richard coleman]

Michael,

I don't think so, but I would love to be proven wrong.  It's rather
annoying to have to open a new query tool window per database and
copy/paste SQL between them.  Especially since the new design doesn't lend
it self to side by side windows.

rik.

On Wed, Jun 19, 2019 at 10:18 AM Michael Shapiro 
wrote:

> PgAdmin3 had the ability to change the connection for an SQL window.
> Does PgAdmin4 have that feature?
>

Re: pgAdmin4 v.4.8 Kubuntu / Chromium can't resize Properties dialog

[richard coleman]

Khushboo,

Thanks, but I think you misunderstood the problem.

[image: pgAdmin4_4.8_table_properties.png]

The horizontal scroll bar doesn't work.  The form *can not* be resized.

The right most column is neither reachable nor fully visible.

Chromium is the basis for;

   - *Chromium*
   - Avast Secure Browser
   - Blisk
   - *Chrome*
   - CodeWeavers CrossOver
   - Comodo Dragon
   - Cốc Cốc
   - Epic Browser
   - Falkon
   - *Microsoft Edge*
   - Opera
   - Qihoo 360 Secure browser
   - Samsung Internet
   - Sleipnir
   - Slimjet
   - SRWare Iron
   - Torch
   - Vivaldi
   - Yandex browser
   - others(?)

It seems rather *silly* to state that Chromium isn't a supported
browser.

Thanks,

rik.


On Wed, Jun 19, 2019 at 12:10 AM Khushboo Vashi <
khushboo.va...@enterprisedb.com> wrote:

> Hi Richard,
>
> On Tue, Jun 18, 2019 at 9:41 PM richard coleman <
> rcoleman.ascen...@gmail.com> wrote:
>
>> To Whom it may concern,
>>
>> Running pgAdmin4 version 4.8 on Chromium under Kubuntu.  When I open the
>> properties dialog for a table, it is un-resizable and the horizontal scroll
>> bar doesn't work.  This is particularly problematic as I can't get to all
>> the properties in the columns screen.
>>
>> The table properties dialog is working fine for me on Chromium on MacOS.
> All the properties of the column can be accessed by expanding the row with
> the Edit icon (Left side) given for each row in the Columns Grid.
>
> I would suggest, try a different browser as well as Chromium is not the
> supported browser for pgAdmin.
>
> You can also log this issue @
> https://redmine.postgresql.org/projects/pgadmin4 if you can't resolve it.
>
> Thanks,
> Khushboo
>
> The developer's tool in Chromium shows these errors/warnings:
>>
>>  3 Unchecked runtime.lastError: Could not establish connection.
>> Receiving end does not exist.
>> vendor.js:93 exported wcDocker
>> vendor.js:155 sprintf() will be removed in the next major release, use
>> the sprintf-js package instead.
>> n @ vendor.js:155
>> :34105/static/js/generated/app.bundle.js?ver=40800:18 Uncaught TypeError:
>> Cannot read property 'chart_obj' of undefined
>> at Object.
>> (:34105/static/js/generated/app.bundle.js?ver=40800:18)
>> at l (vendor.js:39)
>> at Object.fireWith [as resolveWith] (vendor.js:39)
>> at u (vendor.js:39)
>> at XMLHttpRequest. (vendor.js:39)
>> vendor.js?ver=40800:39 [Deprecation] Synchronous XMLHttpRequest on the
>> main thread is deprecated because of its detrimental effects to the end
>> user's experience. For more help, check https://xhr.spec.whatwg.org/.
>>
>> Any thoughts?
>>
>> Thanks,
>>
>> rik.
>>
>>

pgAdmin4 v.4.8 Kubuntu / Chromium can't resize Properties dialog

[richard coleman]

To Whom it may concern,

Running pgAdmin4 version 4.8 on Chromium under Kubuntu.  When I open the
properties dialog for a table, it is un-resizable and the horizontal scroll
bar doesn't work.  This is particularly problematic as I can't get to all
the properties in the columns screen.

The developer's tool in Chromium shows these errors/warnings:

 3 Unchecked runtime.lastError: Could not establish connection. Receiving
end does not exist.
vendor.js:93 exported wcDocker
vendor.js:155 sprintf() will be removed in the next major release, use the
sprintf-js package instead.
n @ vendor.js:155
:34105/static/js/generated/app.bundle.js?ver=40800:18 Uncaught TypeError:
Cannot read property 'chart_obj' of undefined
at Object.
(:34105/static/js/generated/app.bundle.js?ver=40800:18)
at l (vendor.js:39)
at Object.fireWith [as resolveWith] (vendor.js:39)
at u (vendor.js:39)
at XMLHttpRequest. (vendor.js:39)
vendor.js?ver=40800:39 [Deprecation] Synchronous XMLHttpRequest on the main
thread is deprecated because of its detrimental effects to the end user's
experience. For more help, check https://xhr.spec.whatwg.org/.

Any thoughts?

Thanks,

rik.

Re: pgAdmin4 4.8 Kubuntu issues

[richard coleman]

Michel,

On Thu, Jun 6, 2019 at 9:15 AM Michel Feinstein 
wrote:

> *(if the malicious actor can steal the file they can also read the key
> from memory)*
>
> As far as I know it's a lot easier for a program to get access to all the
> files in a system (specially on Windows) than to dump the memory, as there
> are memory barriers protected by the OS (and address randomization) that
> limits the addresses a program has access.
> That would depend on your expected adversary, and the OS you are running
> on.
> Sure there are read/write controls for files as well, but not as
> restrictive as memory barriers.
> This also depends on the OS you are running on, and how your machine's
> been configured.
>

 If you are *really* worried about the state of your saved passwords,
then *don't* let pgAdmin4 (or anything else for that matter) *save* them.
The next best thing would be to encrypt them with a master password that
the program prompts for *every time* it needs to use it.  Otherwise you
might as well tie it to your login password and let the OS handle
decrypting it.  The current implementation gives you the convenience of
saving your connection passwords with a *slight* increase in security at
the cost of locking down the application for everyone else, whether or not
they have *any* saved connection passwords.


> PS: Sorry for not using the fancy colors and reply marks, I am on my
> phone.
>
Feedback always appreciated, lack of color forgiven ;).

>
> rik.
> On Thu, Jun 6, 2019, 10:01 richard coleman 
> wrote:
>
>> Dave,
>>
>> Thank you for getting back to me.
>>
>> On Thu, Jun 6, 2019 at 5:01 AM Dave Page  wrote:
>>
>>>
>>>
>>> On Wed, Jun 5, 2019 at 7:29 PM richard coleman <
>>> rcoleman.ascen...@gmail.com> wrote:
>>>
>>>>
>>>> All passwords are stored in files of one sort or another.  Hopefully
>>>>> those files are effectively encrypted (assuming of course that you had 
>>>>> even
>>>>> had pgAdmin4 save your passwords to begin with).
>>>>>
>>>>
>>> Sure, in pgAdmin 4 they are (unlike pgAdmin 3 which used PostgreSQL's
>>> .pgpass files which are plain text). However, the problem is that unless
>>> the key to encrypt/decrypt those passwords is stored externally (e.g. in
>>> the users brain, or on a Ubikey or similar), it is also in a file.
>>> Then it becomes one more thing for users to forget/write down/reuse
>>> something they already know.
>>>
>>
>>
>>>
>>>
>>>> Now you may have a VPN, but you also may use the same password for
>>>>> different things, or other people might use servers that are less hard to
>>>>> reach.
>>>>>  The same sort of people who use the same password for a number of
>>>>> things are just going to use that self same password as their *master
>>>>> password* in pgAdmin4.
>>>>>
>>>>
>>> Sure - however, I'm not ever going to make the default security in
>>> pgAdmin cater to people who do stupid things like that, or just assume that
>>> people are already doing stupid things so we shouldn't bother. We will
>>> always strive to be secure by default, within the bounds of reasonable user
>>> experience.
>>> The only thing you *might* be securing are saved passwords, *if* the
>>> user has saved any.  By locking up the *entire* application behind the
>>> master password, you are just encouraging bad behavior for little to no
>>> gain.
>>>
>>>> How? pgAdmin has no way of doing that over what is essentially a web
>>>>> application - and even if it did, allowing a remotely accessible
>>>>> application (particularly one in which external programs can be configured
>>>>> and executed by users) to modify it's own configuration is a *really* bad
>>>>> idea.
>>>>>  Well for a start Edge uses Microsoft's user credentials as a master
>>>>> password.  Any number of applications can access files in a *protected
>>>>> area *and prompt for a sudo/administrator credential.
>>>>>
>>>>
>>> We could do that too. Assuming users were happy to setup a Kerberos
>>> infrastructure. Otherwise, we'd need to rely on browser password saving
>>> which isn't always reliable. The browser intentionally doesn't allow us to
>>> access locally held credentials as that would be massively insecure.
>>>
>>>
>>>> As for the

Re: pgAdmin4 4.8 Kubuntu issues

[richard coleman]

Dave,

Thank you for getting back to me.

On Thu, Jun 6, 2019 at 5:01 AM Dave Page  wrote:

>
>
> On Wed, Jun 5, 2019 at 7:29 PM richard coleman <
> rcoleman.ascen...@gmail.com> wrote:
>
>>
>> All passwords are stored in files of one sort or another.  Hopefully
>>> those files are effectively encrypted (assuming of course that you had even
>>> had pgAdmin4 save your passwords to begin with).
>>>
>>
> Sure, in pgAdmin 4 they are (unlike pgAdmin 3 which used PostgreSQL's
> .pgpass files which are plain text). However, the problem is that unless
> the key to encrypt/decrypt those passwords is stored externally (e.g. in
> the users brain, or on a Ubikey or similar), it is also in a file.
> Then it becomes one more thing for users to forget/write down/reuse
> something they already know.
>


>
>
>> Now you may have a VPN, but you also may use the same password for
>>> different things, or other people might use servers that are less hard to
>>> reach.
>>>  The same sort of people who use the same password for a number of
>>> things are just going to use that self same password as their *master
>>> password* in pgAdmin4.
>>>
>>
> Sure - however, I'm not ever going to make the default security in pgAdmin
> cater to people who do stupid things like that, or just assume that people
> are already doing stupid things so we shouldn't bother. We will always
> strive to be secure by default, within the bounds of reasonable user
> experience.
> The only thing you *might* be securing are saved passwords, *if* the user
> has saved any.  By locking up the *entire* application behind the master
> password, you are just encouraging bad behavior for little to no gain.
>
>> How? pgAdmin has no way of doing that over what is essentially a web
>>> application - and even if it did, allowing a remotely accessible
>>> application (particularly one in which external programs can be configured
>>> and executed by users) to modify it's own configuration is a *really* bad
>>> idea.
>>>  Well for a start Edge uses Microsoft's user credentials as a master
>>> password.  Any number of applications can access files in a *protected
>>> area *and prompt for a sudo/administrator credential.
>>>
>>
> We could do that too. Assuming users were happy to setup a Kerberos
> infrastructure. Otherwise, we'd need to rely on browser password saving
> which isn't always reliable. The browser intentionally doesn't allow us to
> access locally held credentials as that would be massively insecure.
>
>
>> As for the choice to make pgAdmin4 a python version of phpPgAdmin,
>>> there's been a lot of discussion, most of it not very favorable.  I
>>> guess you can chalk this up to one more reason converting pgAdmin from an
>>> application to a *web app* was probably not the best idea.
>>>
>>
> Funny that, whilst there certainly have been people who didn't like the
> change, the *vast* majority of feedback I receive has been positive since
> we ironed out the very early performance issues. Downloads are up massively
> as well, and that's before you count the Docker distro that didn't exist
> with pgAdmin 3, which has been over 5M pulls for quite some time now (I
> don't know the banding of Dockers numbers - I assume it'll go to 10M+ at
> some point).
> Are you really basing *popularity* on a comparison to pgAdmin3, the same
> version that isn't supported, and has one Windows only fork that supports
> postgreSQL 10?  If people want a gui to administer postgreSQL 11+, the most
> promoted one is pgAdmin4.  If pgAdmin3 supported postgreSQL 11+ most people
> would still be using it.
> Regardless, I'm happy with the change, and I'm happy in the knowledge that
> most users seem to agree. Those that don't are welcome to use the LTS
> version of pgAdmin 3 if they prefer, or other tools. It's a free world (for
> the most part) - people can and should use what they find most productive
> and useful for them. I will carry on working on and providing (for free)
> the tools that interest me.
> Just go back through the emails on this list alone and read the many
> emails of people writing; pgAdmin3 *did* this, why doesn't pgAdmin4?
> They are not even talking about *new* features, just simple feature
> parity. The most recent one that comes to mind is the decision to *hide* the
> explain results behind a "[".
>
>>
>>>> So basically what we have is a *major* UI change (users are literally
>>>> locked out of the application) caused by upg

Re: pgAdmin4 4.8 Kubuntu issues

[richard coleman]

Dave,

On Wed, Jun 5, 2019 at 12:13 PM Dave Page  wrote:

> Richard,
>
> On Wed, Jun 5, 2019 at 4:55 PM richard coleman <
> rcoleman.ascen...@gmail.com> wrote:
>
>> Dave,
>>
>> Actually I thought I was being quite restrained in my assessment.  With
>> version 4.8 the developers completely upended the end user experience.
>> From pgAdmin3 through all versions of pgAdmin4 *prior to the current one*,
>> the end user could start pgAdmin and then get to work creating connections,
>> modifying databases, running queries as their postgreSQL permissions
>> allowed.  If they wanted to save a password, that was their choice (though
>> it didn't always work).  Suddenly with pgAdmin4 4.8 they are *locked out* of
>> the application by a *required* Master Password.  To make matters worse,
>> there is *no* simple or even well defined way to disable this change.
>> The *solution* is to dig through the documentation, then *rummage* around
>> on your file system (as the exact location varies by OS or distribution)
>> for a *sample* file (the config file isn't actually documented in the
>> official documentation).  *Then* create a brand new file, make sure you
>> include the *magic setting*, restart pgAdmin4 and you will *finally* get
>> back to working the way you did *before* you let pgAdmin4 update itself
>> from 4.7 to 4.8.
>>
>
> I've committed changes to improve the documentation.
>
>
>>
>> The only situation I can envision (and perhaps I'm just not paranoid
>> enough) is if someone breaks into my computer, gets my login credentials,
>> gets the separate login credentials to the VPN I use to connect to the
>> corporate network, and *then* manages to start pgAdmin4 as myself to
>> connect to a postgreSQL database, that I've just happened to have had
>> pgAdmin4 save the password to and commit some sort of mischief with my
>> level of access.
>>
>> So, to summarize an attacker would have had to:
>>
>>1. hack my machine
>>2. hack into the corporate network through my VPN credentials (which
>>they would have to hack)
>>3. run pgAdmin4 *as* me
>>4. have relied on me having pgAdmin4 *save* my passwords.
>>
>> Nope. Way easier than that. A flaw in a browser plugin or browser, or
> effective social engineering, or a malicious application can leak files on
> your system, and as stored passwords are stored in, well, files.
> All passwords are stored in files of one sort or another.  Hopefully those
> files are effectively encrypted (assuming of course that you had even had
> pgAdmin4 save your passwords to begin with).
> Now you may have a VPN, but you also may use the same password for
> different things, or other people might use servers that are less hard to
> reach.
>  The same sort of people who use the same password for a number of things
> are just going to use that self same password as their *master password* in
> pgAdmin4.
>
>> The only thing I gain from the new *Master Password* requirement is that
>> *if* I had pgAdmin4 save my passwords, an attacker would have need to
>> know one more password to *unlock* pgAdmin4.
>>
>> Unfortunately if I *don't* have pgAdmin4 save my passwords, I still have
>> to remember a *Master Password*.  Why?  Without step 4 above, it doesn't
>> actually provide anymore security.
>>
>> To add insult to injury I (like *many* people currently using pgAdmin4)
>> have root access (or Administrator level credentials for those Windows
>> users) to my own machine.  Which means it's possible for me to jump through
>> all of the hoops to disable the *Master Password *mechanism.  So what
>> did not having a setting in the Preferences UI gain in terms of security?
>> If you wanted to restrict changing that setting to users with the required
>> level of access you could have simply gated it with a sudo/administrator
>> credentials dialog.
>>
>
> How? pgAdmin has no way of doing that over what is essentially a web
> application - and even if it did, allowing a remotely accessible
> application (particularly one in which external programs can be configured
> and executed by users) to modify it's own configuration is a *really* bad
> idea.
>  Well for a start Edge uses Microsoft's user credentials as a master
> password.  Any number of applications can access files in a *protected
> area *and prompt for a sudo/administrator credential.  As for the choice
> to make pgAdmin4 a python version of phpPgAdmin, there's been a lot of
> discussion, most of it not very favorable.  I guess you can chalk this up
> to o

Re: pgAdmin4 4.8 Kubuntu issues

[richard coleman]

Michel,

I appreciate your taking the time to weigh in on this.  As I mentioned
previously, I can understand why this feature was added, other applications
have a "*master password to protect other saved passwords*"
feature.   Chrome *used to* before they went to protecting it with your
Google account.  Firefox (FF) still does.  The problem as I see it was in
the implementation.  In FF it's opt-in, and basically transparent to the
user.  Unless you want to *view* the saved passwords in plain text, none of
the features are effected.  Contrast that with how pgAdmin4 has chosen to
implement it.  It's a *painful* opt-out and it locks nearly everything
except the preferences regardless of whether or not you've had pgAdmin4
save *any* passwords at all.  Basically the developers have decided that
you are going to use this new *Master Password* mechanism or you are not
going to have access to the program or any of the server connections you've
already created.  One day you are going along using pgAdmin4, then there's
an update.  You update pgAdmin4 and *Bam!* You *must* enter a master
password, or else.  Now you are posting on lists like this one, or scouring
the internet looking for some way to turn this stupid thing off. Or you're
just going to enter something like "a" as your password (or "password", or
the exact same password you use to login/email/and everything else).

I feel it was *badly* handled.  No warning, painful opt-out, locks *way too
much* functionality.

I really do hope the devs reconsider this poor decision.

rik.



On Wed, Jun 5, 2019 at 1:27 PM Michel Feinstein 
wrote:

> Hi Richard,
>
> I am jumping-in specially because I am the guy to blame for this new
> feature. I identified the security risks and reported it, so I understand
> your frustration and feel bad that your work flow is not as comfortable as
> it was before. I hate when this happens to me.
>
> I also think that using the OS method for storing secrets would be more
> desirable, but I also understand this is way harder to achieve, since there
> would be Windows, Linux and Mac specific code into the project, which is
> way harder to develop than a simple Master Password.
>
> In my particular case, I have some very big alphanumeric passwords for my
> database users and a more user-friendly Master Password on my machine.
> Having to remember the database passwords is a pain, so I store them
> encrypted, so having a simpler Master Password is a very convenient
> solution for my use case, as I don't trust any passwords to be stored
> without encryption.
>
> I am not a developer into the pgAdmin project, I am just pointing out how
> this feature can be good and help some people, while improving security.
>
> I would argue that this discussion on opt-in VS opt-out should be
> investigated according to user impact. If lots of people complain, than
> this should be changed, if they don't, then keep it, as it's more secure. I
> know it's not going to help in your case, but seems more balanced to me on
> security vs. Usage, on a more democratic way.
>
> And again, I think the docs should explain this at length.
>
> Sorry if my input wasn't very helpful on your use case.
>
> Michel.
>
> On Wed, Jun 5, 2019, 14:03 richard coleman 
> wrote:
>
>> Michel,
>>
>> Thanks for jumping into the conversation.
>>
>> On Wed, Jun 5, 2019 at 12:18 PM Michel Feinstein <
>> michelfeinst...@gmail.com> wrote:
>>
>>> Let me just add some points to the discussion:
>>>
>>> 1 - Your use case is different than most people, you have a VPN in the
>>> middle of your workflow. Besides, you are imaging someone breaking into
>>> your computer, but the attack vector is much simpler than that.
>>>
>>> Someone can craft a malware that will automatically scan for pgAdmin
>>> passwords, upon arriving on any machine, and send whatever it's found to
>>> his creator. This could spread all over the internet, and one of your
>>> employees with less security awareness could click the wrong email
>>> attachment and then leak his database credentials. Google employees have
>>> been victim to physhing attacks (that's why they use smart cards now), I
>>> can't imagine this won't happen somewhere else.
>>>
>>> Yep, that *could* happen.  But the proposed solution is to add yet
>> *another* password?  If the developers were *truly *trying to increase
>> the security of pgAdmin4 from this attack vector, the simplest solution
>> would be to *remove* the ability of pgAdmin4 to save passwords.  Many of
>> our machines use ip or other non-password based security to

Re: pgAdmin4 4.8 Kubuntu issues

[richard coleman]

Michel,

Thanks for jumping into the conversation.

On Wed, Jun 5, 2019 at 12:18 PM Michel Feinstein 
wrote:

> Let me just add some points to the discussion:
>
> 1 - Your use case is different than most people, you have a VPN in the
> middle of your workflow. Besides, you are imaging someone breaking into
> your computer, but the attack vector is much simpler than that.
>
> Someone can craft a malware that will automatically scan for pgAdmin
> passwords, upon arriving on any machine, and send whatever it's found to
> his creator. This could spread all over the internet, and one of your
> employees with less security awareness could click the wrong email
> attachment and then leak his database credentials. Google employees have
> been victim to physhing attacks (that's why they use smart cards now), I
> can't imagine this won't happen somewhere else.
>
> Yep, that *could* happen.  But the proposed solution is to add yet
*another* password?  If the developers were *truly *trying to increase the
security of pgAdmin4 from this attack vector, the simplest solution would
be to *remove* the ability of pgAdmin4 to save passwords.  Many of our
machines use ip or other non-password based security to control access to
our databases.  pgAdmin could force some other non-password security if the
user wanted to save their credentials.  Or pgAdmin could save their
credentials protected by the same mechanism the OS saves user
credentials.

Many companies don't have their databases behind a VPN, specially in cloud
> environments (some use a VPC, some don't for many reasons, not related to
> this topic).
>
> Besides, I could be wrong, but I think a malware on your computer could
> read your pgAdmin passwords, then submit queries to your company's database
> from inside your own computer, since it's already connected to your VPN,
> and then send back to the attacker the results, so it won't have to steal
> any VPN credentials, just use your own connection as a bridge. It doesn't
> have to target you specifically, just send a ping back whenever it detects
> pgAdmin passwords in a machine and then go to "Bridge mode". I might be
> wrong since I almost never use a VPN and am not used to its inner workings.
>
>  Which just goes back to my earlier point of; 'if that's what you are
worried about, then don't let users save passwords'.

> 2 - I think the opt-out should be more streamlined, the security risks
> should be better informed and the Master Password should only be asked if
> the user decided to save a password in the first place.
>

I think it should be an *opt-in*.  That's how most other applications that
utilize a master password work.

>
> 3 - pgAdmin could create an empty configuration file by default, so it
> would be easier to locate it in all Linux distributions.
>
> It shouldn't need one, the user should be able to use or not use a master
password from the Preferences UI.  If they want to use one, fine.  If not,
that's OK too.  If they were and want to stop, warn the user and wipe all
of the existing passwords.

> Those are my 2 cents.
>
> Thanks again,

rik.

> On Wed, Jun 5, 2019, 12:55 richard coleman 
> wrote:
>
>> Dave,
>>
>> Actually I thought I was being quite restrained in my assessment.  With
>> version 4.8 the developers completely upended the end user experience.
>> From pgAdmin3 through all versions of pgAdmin4 *prior to the current one*,
>> the end user could start pgAdmin and then get to work creating connections,
>> modifying databases, running queries as their postgreSQL permissions
>> allowed.  If they wanted to save a password, that was their choice (though
>> it didn't always work).  Suddenly with pgAdmin4 4.8 they are *locked out* of
>> the application by a *required* Master Password.  To make matters worse,
>> there is *no* simple or even well defined way to disable this change.
>> The *solution* is to dig through the documentation, then *rummage* around
>> on your file system (as the exact location varies by OS or distribution)
>> for a *sample* file (the config file isn't actually documented in the
>> official documentation).  *Then* create a brand new file, make sure you
>> include the *magic setting*, restart pgAdmin4 and you will *finally* get
>> back to working the way you did *before* you let pgAdmin4 update itself
>> from 4.7 to 4.8.
>>
>> The only situation I can envision (and perhaps I'm just not paranoid
>> enough) is if someone breaks into my computer, gets my login credentials,
>> gets the separate login credentials to the VPN I use to connect to the
>> corporate network, and *then* manages to start pgAdmin

Re: pgAdmin4 4.8 Kubuntu issues

[richard coleman]

Dave,

Actually I thought I was being quite restrained in my assessment.  With
version 4.8 the developers completely upended the end user experience.
>From pgAdmin3 through all versions of pgAdmin4 *prior to the current one*,
the end user could start pgAdmin and then get to work creating connections,
modifying databases, running queries as their postgreSQL permissions
allowed.  If they wanted to save a password, that was their choice (though
it didn't always work).  Suddenly with pgAdmin4 4.8 they are *locked out* of
the application by a *required* Master Password.  To make matters worse,
there is *no* simple or even well defined way to disable this change.  The
*solution* is to dig through the documentation, then *rummage* around on
your file system (as the exact location varies by OS or distribution) for a
*sample* file (the config file isn't actually documented in the official
documentation).  *Then* create a brand new file, make sure you include
the *magic
setting*, restart pgAdmin4 and you will *finally* get back to working the
way you did *before* you let pgAdmin4 update itself from 4.7 to 4.8.

The only situation I can envision (and perhaps I'm just not paranoid
enough) is if someone breaks into my computer, gets my login credentials,
gets the separate login credentials to the VPN I use to connect to the
corporate network, and *then* manages to start pgAdmin4 as myself to
connect to a postgreSQL database, that I've just happened to have had
pgAdmin4 save the password to and commit some sort of mischief with my
level of access.

So, to summarize an attacker would have had to:

   1. hack my machine
   2. hack into the corporate network through my VPN credentials (which
   they would have to hack)
   3. run pgAdmin4 *as* me
   4. have relied on me having pgAdmin4 *save* my passwords.

The only thing I gain from the new *Master Password* requirement is that
*if* I had pgAdmin4 save my passwords, an attacker would have need to know
one more password to *unlock* pgAdmin4.

Unfortunately if I *don't* have pgAdmin4 save my passwords, I still have to
remember a *Master Password*.  Why?  Without step 4 above, it doesn't
actually provide anymore security.

To add insult to injury I (like *many* people currently using pgAdmin4)
have root access (or Administrator level credentials for those Windows
users) to my own machine.  Which means it's possible for me to jump through
all of the hoops to disable the *Master Password *mechanism.  So what did
not having a setting in the Preferences UI gain in terms of security?  If
you wanted to restrict changing that setting to users with the required
level of access you could have simply gated it with a sudo/administrator
credentials dialog.

So basically what we have is a *major* UI change (users are literally
locked out of the application) caused by upgrading a minor version level
(4.7 to 4.8) with no simple way to revert the behavior all for a dubious
increase in security.

Yes, I think I have been quite restrained in my assessment.

Thanks,

rik.



On Wed, Jun 5, 2019 at 10:59 AM Dave Page  wrote:

> Richard,
>
> On Wed, Jun 5, 2019 at 3:22 PM richard coleman <
> rcoleman.ascen...@gmail.com> wrote:
>
>> Dave,
>>
>> And where would *that* be?  pgAdmin4 the executable and the shared
>> library is located in /usr/bin/.  There are *no* entries in /etc/ for
>> pgAdmin4.  There is a pgadmin4.db in /home/u/.pgadmin/  but *no* config
>> files of any kind there either.
>>
>
> I have no idea, I don't use Ubuntu or any of it's derivatives and don't
> know where it installs. Have you tried searching for config.py? That is
> *not* optional, and must exist.
>
>
>> So it's looking like the only way to actually *use *the current version
>> of pgAdmin4 is to create an undocumented file (the help page says you can
>> use config.py as a reference, but guess what?  That file doesn't exist
>> either.) in an unknown location, and manually add the magic string;
>>
>> "*MASTER_PASSWORD_REQUIRED=False"*
>>
>>
> I think that's a little hyperbolic don't you? It works as intended, with
> no changes required if you set the password and re-enter it when you
> restart pgAdmin. You only need to modify anything if you want to change the
> behaviour.
>
> And to be clear; if config.py is not present on your system, then there is
> no way pgAdmin will even start, let alone work.
>
>
>>
>> I get *why* you added this feature, but I think it was implemented 
>> *completely
>> backwards*.  Instead of making *every* end user jump through these
>> ridiculous hoops just to *continue* to use pgAdmin4 as they had been up
>> to this point, a better option would be to allow security conscious sys
>> admins to add the configuration:
>

Re: pgAdmin4 4.8 Kubuntu issues

[richard coleman]

Dave,

Sorry, but after an e*xhaustive* search of the several terabytes on my
machine, there is *no* config_local.py file.  Do you have any idea where
it's supposed to be located?

Thanks,

rik.

On Wed, Jun 5, 2019 at 9:30 AM Dave Page  wrote:

>
>
> On Wed, Jun 5, 2019 at 1:16 PM richard coleman <
> rcoleman.ascen...@gmail.com> wrote:
>
>> Cherio,
>>
>> I am sorry to inform you, but there is *no* mention of "config_local.py"
>> on that page, nor any indication of where I would find it.
>>
>
>
> https://www.pgadmin.org/docs/pgadmin4/4.x/desktop_deployment.html#configuration
>
>
>>
>> rik.
>>
>> On Tue, Jun 4, 2019 at 5:06 PM Cherio  wrote:
>>
>>> Put "MASTER_PASSWORD_REQUIRED = False" line into your
>>> "lib/python?.?/site-packages/pgadmin4/config_local.py". This is in the
>>> docs: https://www.pgadmin.org/docs/pgadmin4/dev/master_password.html
>>>
>>> On Tue, Jun 4, 2019 at 4:41 PM richard coleman <
>>> rcoleman.ascen...@gmail.com> wrote:
>>>
>>>> To whomever,
>>>>
>>>> Running a newly update pgAdmin 4 version 4.8 on my Kubuntu box.  There
>>>> are a couple of glaring issues.
>>>>
>>>> First: It keeps prompting to; "Set Master Password"
>>>> I don't want to set another password that I'll just end up
>>>> forgetting.
>>>>
>>>> Second: When I click the "?" button on that dialog box it takes me to
>>>> this page:
>>>> "http://127.0.0.1:33681/help/help/master_password.html";
>>>> Which returns "404 Not Found"
>>>>
>>>> Hopefully there is a simple solution to these issues.
>>>>
>>>> Thanks,
>>>>
>>>> rik.
>>>>
>>>
>
> --
> Dave Page
> Blog: http://pgsnake.blogspot.com
> Twitter: @pgsnake
>
> EnterpriseDB UK: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>

Re: pgAdmin4 4.8 Kubuntu issues

[richard coleman]

Cherio,

I am sorry to inform you, but there is *no* mention of "config_local.py" on
that page, nor any indication of where I would find it.

rik.

On Tue, Jun 4, 2019 at 5:06 PM Cherio  wrote:

> Put "MASTER_PASSWORD_REQUIRED = False" line into your
> "lib/python?.?/site-packages/pgadmin4/config_local.py". This is in the
> docs: https://www.pgadmin.org/docs/pgadmin4/dev/master_password.html
>
> On Tue, Jun 4, 2019 at 4:41 PM richard coleman <
> rcoleman.ascen...@gmail.com> wrote:
>
>> To whomever,
>>
>> Running a newly update pgAdmin 4 version 4.8 on my Kubuntu box.  There
>> are a couple of glaring issues.
>>
>> First: It keeps prompting to; "Set Master Password"
>> I don't want to set another password that I'll just end up forgetting.
>>
>> Second: When I click the "?" button on that dialog box it takes me to
>> this page:
>> "http://127.0.0.1:33681/help/help/master_password.html";
>> Which returns "404 Not Found"
>>
>> Hopefully there is a simple solution to these issues.
>>
>> Thanks,
>>
>> rik.
>>
>

Re: pgAdmin4 4.8 Kubuntu issues

[richard coleman]

Christoph,

pgAdmin4 updated itself this morning, and now the "?" on the Set Master
Password dialog returns an actual page, not a 404.  Unfortunately it isn't
all that clear.  It suggests;

"You can disable the master password by setting the configuration parameter
MASTER_PASSWORD_REQUIRED=False"

but there is no such setting in the Preferences UI of pgAdmin and it
doesn't direct me to the proper config file either.

Thanks,

rik.

On Wed, Jun 5, 2019 at 5:15 AM Christoph Berg  wrote:

> Re: Dave Page 2019-06-05  agzdhljj...@mail.gmail.com>
> > > Second: When I click the "?" button on that dialog box it takes me to
> this
> > > page:
> > > "http://127.0.0.1:33681/help/help/master_password.html";
> > > Which returns "404 Not Found"
> > >
> >
> > That sounds like an issue with the packaging - that file is certainly
> there
> > in the source, and works when I click the button (though I do not use the
> > Ubuntu packages).
>
> Hi Richard,
>
> do you have the pgadmin4-doc package installed?
>
> At the moment, it is "Suggested" by pgadmin4-common. I'll promote that
> to a "Recommends".
>
> Christoph
>

pgAdmin4 4.8 Kubuntu issues

[richard coleman]

To whomever,

Running a newly update pgAdmin 4 version 4.8 on my Kubuntu box.  There are
a couple of glaring issues.

First: It keeps prompting to; "Set Master Password"
I don't want to set another password that I'll just end up forgetting.

Second: When I click the "?" button on that dialog box it takes me to this
page:
"http://127.0.0.1:33681/help/help/master_password.html";
Which returns "404 Not Found"

Hopefully there is a simple solution to these issues.

Thanks,

rik.

Re: pip, anyone?

[richard coleman]

Malik,

Well for what it's worth, I'm running Kubuntu 18.10 and I usually apt-get
install pgAdmin4.  The instructions on how to add the relevant repository
is here: https://wiki.postgresql.org/wiki/Apt .

The only caveat is that it tends to lag behind the releases for windows and
RPM (sometimes even skipping a version or two).

Good luck,

rik.

On Tue, May 7, 2019 at 6:31 PM Malik Rumi  wrote:

> So I am finally getting around to upgrading my pgadmin4, and I was a
> little confused about the 'best' way to install or upgrade. The answer to
> this question may be out there, but I didn't see it.
>
> I checked pypi, and a search for pgadmin4 came up empty. But I have seen
> blogs and tutorials (out of date?) make reference to doing a pip install.
> And yet, on postgresql.org, my search led me to downloading a wheel
> (which, if memory serves, is how I got my current version) with no
> reference to pip install. But then how did I get all the dependencies? Are
> they in the wheel, too?
>
> There is also, apparently, apt-get (I'm on Ubuntu 18.04 with Postgresql
> 11.2).
>
> If there is a simple but up to date explanation of all this out there,
> feel free to just link to it in your response instead of writing out the
> answer here. Thanks.
>
>
>
> *“None of you has faith until he loves for his brother or his neighbor
> what he loves for himself.”*
>

Re: pgadmin 4 v4.6 - Eternal Loading

[richard coleman]

Maycon,

Thanks for sharing the information regardless.

rik.

On Fri, May 3, 2019 at 9:23 AM Maycon Oleczinski 
wrote:

> Hi Richard.
>
> It's a specific for our usage:
> OutSystems Launcher
>
> But via DevTools console can be possible view if any impact.
> In this case, ".js" extension's file name display right to an "outsystems"
> reference.
>
> Regards.
>
> Maycon
>
> Em sex, 3 de mai de 2019 às 10:19, richard coleman <
> rcoleman.ascen...@gmail.com> escreveu:
>
>> Maycon,
>>
>> If you wouldn't mind sharing, which Chrome Extension was the cause?
>>
>> Thanks,
>>
>> rik.
>>
>> On Fri, May 3, 2019 at 9:18 AM Maycon Oleczinski 
>> wrote:
>>
>>> Hi All.
>>>
>>> Sorry, attach has blocked.
>>> But just now, really now, I found "problem cause".
>>> An Chrome Extension activated when page load get error to analyze
>>> pgAdmin page, crash and stop load.
>>>
>>> I've deactivate this extension and done!
>>>
>>> I can saw this extension via DevTools (F12) console.
>>>
>>> Tnx'o'mch by attention!!
>>>
>>> Regards.
>>> Maycon
>>>
>>>
>>>
>>> Em sex, 3 de mai de 2019 às 05:07, Durumdara 
>>> escreveu:
>>>
>>>> Hello!
>>>>
>>>> I have same problem. 4.5 worked well. I updated to 4.6, and then I got
>>>> waiting messages in splash, and more minutes later the server exits.
>>>> Windows 10 prof. I have to reinstall 4.5 because I must work.
>>>>
>>>> dd
>>>>
>>>> Aditya Toshniwal  ezt írta
>>>> (időpont: 2019. máj. 3., P, 5:19):
>>>>
>>>>> Hi Maycon,
>>>>>
>>>>> I guess you missed the attachment.
>>>>> Could you please check if you are getting error in browser console ?
>>>>> Right Click and click on inspect element.
>>>>>
>>>>> On Thu, May 2, 2019 at 10:14 PM Maycon Oleczinski <
>>>>> maycon.o...@gmail.com> wrote:
>>>>>
>>>>>> Hi All.
>>>>>>
>>>>>> I've installed pgAdmin 4 v4.6 in my laptop and it in eternal loading
>>>>>> (see image attached).
>>>>>>
>>>>>> Has anyone a trick to make it work?
>>>>>>
>>>>>> Note: with previous versions it occurs too.
>>>>>>
>>>>>> *Hardware:*
>>>>>> LeNovo Thinkpad L440
>>>>>> HD 240 SSD Kingston
>>>>>> 16GB RAM
>>>>>> Intel Core i5 vPro i-4300M
>>>>>>
>>>>>> *OS:*
>>>>>> Windows 10 Profissional
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Thanks and Regards,
>>>>> Aditya Toshniwal
>>>>> Software Engineer | EnterpriseDB Software Solutions | Pune
>>>>> "Don't Complain about Heat, Plant a tree"
>>>>>
>>>>

Re: pgadmin 4 v4.6 - Eternal Loading

[richard coleman]

Maycon,

If you wouldn't mind sharing, which Chrome Extension was the cause?

Thanks,

rik.

On Fri, May 3, 2019 at 9:18 AM Maycon Oleczinski 
wrote:

> Hi All.
>
> Sorry, attach has blocked.
> But just now, really now, I found "problem cause".
> An Chrome Extension activated when page load get error to analyze pgAdmin
> page, crash and stop load.
>
> I've deactivate this extension and done!
>
> I can saw this extension via DevTools (F12) console.
>
> Tnx'o'mch by attention!!
>
> Regards.
> Maycon
>
>
>
> Em sex, 3 de mai de 2019 às 05:07, Durumdara 
> escreveu:
>
>> Hello!
>>
>> I have same problem. 4.5 worked well. I updated to 4.6, and then I got
>> waiting messages in splash, and more minutes later the server exits.
>> Windows 10 prof. I have to reinstall 4.5 because I must work.
>>
>> dd
>>
>> Aditya Toshniwal  ezt írta (időpont:
>> 2019. máj. 3., P, 5:19):
>>
>>> Hi Maycon,
>>>
>>> I guess you missed the attachment.
>>> Could you please check if you are getting error in browser console ?
>>> Right Click and click on inspect element.
>>>
>>> On Thu, May 2, 2019 at 10:14 PM Maycon Oleczinski 
>>> wrote:
>>>
 Hi All.

 I've installed pgAdmin 4 v4.6 in my laptop and it in eternal loading
 (see image attached).

 Has anyone a trick to make it work?

 Note: with previous versions it occurs too.

 *Hardware:*
 LeNovo Thinkpad L440
 HD 240 SSD Kingston
 16GB RAM
 Intel Core i5 vPro i-4300M

 *OS:*
 Windows 10 Profissional

>>>
>>>
>>> --
>>> Thanks and Regards,
>>> Aditya Toshniwal
>>> Software Engineer | EnterpriseDB Software Solutions | Pune
>>> "Don't Complain about Heat, Plant a tree"
>>>
>>

Re: How to: copy records from one table to another?

[richard coleman]

Dave,

When moving data *between* postgresql databases, I rely on custom python
scripts using psycopg2.  A simple write loop inside a read loop and two
connections usually does the trick.

rik.

On Fri, Mar 22, 2019 at 9:59 AM Dave Caughey  wrote:

> Unfortunately, using simple SQL statements isn't an option when dealing
> with multiple databases (e.g., moving records from a development
> environment into a production system as per my proposed use case).
>
> Cheers,
> Dave
>
>
> On Fri, Mar 22, 2019 at 9:18 AM Calle Hedberg 
> wrote:
>
>> Dave,
>>
>> You are talking about "copying" data from one table to another table in
>> the same database, yes?
>>
>> For that use an INSERT INTO  (SELECT .FROM
>> sourcetable) query - it will provide most of the flexibility you need with
>> regard to including/excluding columns, renaming, changing column order, etc.
>>
>> If you need to do several sequential manipulation steps on the data to be
>> copied, it might be necessary to first insert the data into a temporary
>> table, then do whatever manipulations necessary, before inserting the final
>> result into the destination table (or if not absolutely necessary, at least
>> easier - while advanced manipulation can be done in a single step, it might
>> require advanced skills and a crystal clear understanding of the underlying
>> processes, and doing it step by step can be safer/easier for us normal
>> mortals...)
>>
>> Regards
>> Calle
>>
>> On Fri, 22 Mar 2019 at 13:36, Dave Caughey  wrote:
>>
>>> Sorry, for the basic question, but I'm not sure if there are bug(s) in
>>> pgAdmin, or just that I'm clueless.  (My money lies on the latter!)
>>>
>>> Imagine the scenario where you are adding a feature to a product that
>>> requires adding some new rows to a configuration table, and as part of the
>>> patch you need to replicate a bunch of record from your development
>>> database to your production databases.
>>>
>>> You'd think there'd be a number of options, e.g.,
>>>
>>> 1. After doing a "View/Edit..." | "Filter by", select the displayed
>>> records, click "copy" to get them on to the clipboard, then go to the
>>> production database, do a "View/Edit..." on the corresponding table, and
>>> paste.  But, in my case, I need my auto-sequenced "id" column to be omitted
>>> (so it gets re-generated in the new table), so perhaps this isn't the right
>>> choice.  Even worse, over the years, my database tables (auto-created via
>>> Hibernate used in a Java Servlet) no longer have the same column order.
>>> (Question: is there no way that copy-and-paste between tables can consider
>>> the column names so copying between (int id,int feature_id,text name) and
>>> (int id,text name,int feature_id) is possible?)
>>>
>>> 2. Or, I could right-click on the table and use Import/Export..."
>>> (Question: is there a way to filter the records that will get exported?
>>>  Or is there a way to trigger import/export on the results of a
>>> "View/Edit..." | "Filter by"?).  However, here the issue is the columns no
>>> longer have the same order (e.g., (int,int,text) vs (int,text,int)) so
>>> "Import/Export..." fails.  (Question: Is that not what the "Header" toggle
>>> is supposed to do?   I see that enabling it during export *adds* a header
>>> to the export files, but shouldn't enabling it during import cause it to be
>>> used to identify the order?).  This method has the attraction that I can
>>> use the "Columns" tab to exclude one of the columns from my export (i.e.,
>>> my auto-sequenced "id" column).
>>>
>>> 3. Or, I could do a "Backup..." and then a corresponding "Restore..." ,
>>> but I noticed that there the generated file contains CREATE DATABASE bits
>>> of code even though the "Include CREATE DATABASE" toggle in the Backup..."
>>> dialog is set to "No" (Question: bug, or my misunderstanding?).  But I'm
>>> guessing that a backup/restore will generally do a complete and utter
>>> restore, rather than just moving some data.
>>>
>>> 4. Other options?
>>>
>>> So, what is the best/simplest way to copy data between tables, given the
>>> possibility that some/all might apply?
>>>
>>>- The columns may be in a different order in different databases
>>>- One column might need be left blank
>>>- I only want to copy some of the records
>>>
>>> Cheers,
>>> Dave
>>>
>>
>>
>> --
>>
>> *Carl-Anders (Calle) Hedberg*
>>
>> HISP
>>
>> Researcher & Technical Specialist
>>
>> Health Information Systems Programme – South Africa
>>
>> Cell:+47 41461011 (Norway)
>>
>> Iridium SatPhone: +8816-315-19119 (usually OFF)
>>
>> E-mail1: ca...@hisp.org
>>
>> E-mail2: calle.hedb...@gmail.com
>>
>> Skype:  calle_hedberg
>>
>

Re: How to: copy records from one table to another?

[richard coleman]

Dave,

If you are talking about copying records between tables in *different*
databases,
postgresql currently doesn't support this.  If you are talking about
*within* the same database, 'INSERT with a SELECT CLAUSE', 'SELECT INTO',
and similar commands exist.

As far as I know;
#1 Sounds good in theory, doesn't really work in practice so I can see why
you can't do it in pgAdmin.
#2 That would be a cool feature.  You can already specify the column(s) to
export.  Perhaps you want to put in a feature request.
#3.Yep. that's my understanding too.  Like using dynamite to remove a
splinter.
#4 Use SQL Statements *designed for this* in a query window (see above).

In the end pgAdmin is *nice* but no substitute for some good ol' fashioned
SQL.  Just open up a query tool window and go to town.

I hope that helps,

rik.

On Fri, Mar 22, 2019 at 8:36 AM Dave Caughey  wrote:

> Sorry, for the basic question, but I'm not sure if there are bug(s) in
> pgAdmin, or just that I'm clueless.  (My money lies on the latter!)
>
> Imagine the scenario where you are adding a feature to a product that
> requires adding some new rows to a configuration table, and as part of the
> patch you need to replicate a bunch of record from your development
> database to your production databases.
>
> You'd think there'd be a number of options, e.g.,
>
> 1. After doing a "View/Edit..." | "Filter by", select the displayed
> records, click "copy" to get them on to the clipboard, then go to the
> production database, do a "View/Edit..." on the corresponding table, and
> paste.  But, in my case, I need my auto-sequenced "id" column to be omitted
> (so it gets re-generated in the new table), so perhaps this isn't the right
> choice.  Even worse, over the years, my database tables (auto-created via
> Hibernate used in a Java Servlet) no longer have the same column order.
> (Question: is there no way that copy-and-paste between tables can consider
> the column names so copying between (int id,int feature_id,text name) and
> (int id,text name,int feature_id) is possible?)
>
> 2. Or, I could right-click on the table and use Import/Export..."
> (Question: is there a way to filter the records that will get exported?
>  Or is there a way to trigger import/export on the results of a
> "View/Edit..." | "Filter by"?).  However, here the issue is the columns no
> longer have the same order (e.g., (int,int,text) vs (int,text,int)) so
> "Import/Export..." fails.  (Question: Is that not what the "Header" toggle
> is supposed to do?   I see that enabling it during export *adds* a header
> to the export files, but shouldn't enabling it during import cause it to be
> used to identify the order?).  This method has the attraction that I can
> use the "Columns" tab to exclude one of the columns from my export (i.e.,
> my auto-sequenced "id" column).
>
> 3. Or, I could do a "Backup..." and then a corresponding "Restore..." ,
> but I noticed that there the generated file contains CREATE DATABASE bits
> of code even though the "Include CREATE DATABASE" toggle in the Backup..."
> dialog is set to "No" (Question: bug, or my misunderstanding?).  But I'm
> guessing that a backup/restore will generally do a complete and utter
> restore, rather than just moving some data.
>
> 4. Other options?
>
> So, what is the best/simplest way to copy data between tables, given the
> possibility that some/all might apply?
>
>- The columns may be in a different order in different databases
>- One column might need be left blank
>- I only want to copy some of the records
>
> Cheers,
> Dave
>

pgAdmin 4.3 scratch pad

[richard coleman]

Hi All,

Is there a setting to *stop* the scratch pad from showing up *every time *you
open a query window?

pgAdmin 4.3, Kubuntu 18.10, Chromium

Thanks,

rik.