Re: Wonderful PgAdmin

2021-10-25 Thread bw
Very dear Developers of pgAdmin!

This goes for me too! Congrats on this magnificent beauty application! It
helped me going deeper into PostgreSQL.
Normally you get only the bugs eating away rotten apples but the tree is
full of shiny  juicy delicious apples!
So I am very happy with the tool and your devotion to pgAdmin. I've been
using it for years, not for nothing :)

Warmth from Brussels!

Bastiaan


On Mon, 25 Oct 2021 at 13:19, Edson Richter 
wrote:

> I'm also grateful for the great work done so far!
>
>
>
> Regards,
>
>
>
> Enviado do Email 
> para Windows
>
>
>
> *De: *Paulo Toledo 
> *Enviado:*segunda-feira, 25 de outubro de 2021 07:39
> *Para: *pgadmin-support@lists.postgresql.org; Rahul Shirsat
> 
> *Assunto: *Wonderful PgAdmin
>
>
>
> Hello,
> I'm just writing to thank you for the great job you all are doing on
> pgAdmin.
> I'm very excited about the ERD tool evolutions.
> Congratulations to everyone.
>
> Paulo Alfredo
>
>
>
>
>


Re: Reorder servers?

2021-10-25 Thread Ray O'Donnell

On 25/10/2021 05:30, Khushboo Vashi wrote:
On 6.1, the object listing order is alphanumeric, so it should work, 
please clear your browser cache and check again.


Hello Khushboo - thanks for responding. I should have been clearer; I'm 
using the desktop version of pgAdmin, rather than a browser. It's 
pgAdmin 6.1 on Ubuntu (actually Kubuntu) 21.04 (Hirsute), installed from 
the package "pgadmin4-desktop" from the pgAdmin apt repo.


Anyway, having posted about the issue, when I started up pgAdmin today 
(after a cold start of the laptop), the servers were in fact sorted 
alphabetically, as I'd expect them to be! Sigh


I wonder if it's related to this issue:

https://redmine.postgresql.org/issues/6955

I won't create a new issue for the moment. However, it would be nice to 
be able to rearrange the servers to an arbitrary order.


Thanks again,

Ray.



--
Raymond O'Donnell // Galway // Ireland
r...@rodonnell.ie




RES: Wonderful PgAdmin

2021-10-25 Thread Edson Richter
I'm also grateful for the great work done so far!

Regards,

Enviado do Email para Windows

De: Paulo Toledo
Enviado:segunda-feira, 25 de outubro de 2021 07:39
Para: 
pgadmin-support@lists.postgresql.org;
 Rahul Shirsat
Assunto: Wonderful PgAdmin

Hello,
I'm just writing to thank you for the great job you all are doing on
pgAdmin.
I'm very excited about the ERD tool evolutions.
Congratulations to everyone.

Paulo Alfredo






Re: Copy error

2021-10-25 Thread Fahar Abbas
Hi Grace,
This email is related to pgAdmin4, Can you please raise this issue on
pgsql-b...@lists.postgresql.org?

On Mon, Oct 25, 2021 at 3:39 PM Grace  wrote:

> Hello,
>
> I am taking a data analysis class and was given a project. I am having
> errors when trying to execute the command. how can I fix this issue? I have
> a windows 10.
>
> ERROR: could not open file "C:\Users\Public\Documents\PostgreSQL
> 10\Documentation\" for reading: No such file or directory HINT: COPY FROM
> instructs the PostgreSQL server process to read a file. You may want a
> client-side facility such as psql's \copy. SQL state: 58P01
>


-- 
Fahar Abbas
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: Copy error

2021-10-25 Thread Aditya Toshniwal
Hi Grace,

What command are you executing ? Please provide more details.

On Mon, Oct 25, 2021 at 4:09 PM Grace  wrote:

> Hello,
>
> I am taking a data analysis class and was given a project. I am having
> errors when trying to execute the command. how can I fix this issue? I have
> a windows 10.
>
> ERROR: could not open file "C:\Users\Public\Documents\PostgreSQL
> 10\Documentation\" for reading: No such file or directory HINT: COPY FROM
> instructs the PostgreSQL server process to read a file. You may want a
> client-side facility such as psql's \copy. SQL state: 58P01
>


-- 
Thanks,
Aditya Toshniwal
pgAdmin Hacker | Software Architect | *edbpostgres.com*

"Don't Complain about Heat, Plant a TREE"


Re: Wonderful PgAdmin

2021-10-25 Thread Aditya Toshniwal
On Mon, Oct 25, 2021 at 4:09 PM Paulo Toledo 
wrote:

> Hello,
> I'm just writing to thank you for the great job you all are doing on
> pgAdmin.
> I'm very excited about the ERD tool evolutions.
> Congratulations to everyone.
>
Nice to hear that. Thanks. :)

>
> Paulo Alfredo
>
>
>
>
>

-- 
Thanks,
Aditya Toshniwal
pgAdmin Hacker | Software Architect | *edbpostgres.com*

"Don't Complain about Heat, Plant a TREE"


Re: Wonderful PgAdmin

2021-10-25 Thread Dave Page
On Mon, Oct 25, 2021 at 11:39 AM Paulo Toledo 
wrote:

> Hello,
> I'm just writing to thank you for the great job you all are doing on
> pgAdmin.
> I'm very excited about the ERD tool evolutions.
> Congratulations to everyone.
>

You're welcome - glad you like it!

-- 
Dave Page
Blog: https://pgsnake.blogspot.com
Twitter: @pgsnake

EDB: https://www.enterprisedb.com


Copy error

2021-10-25 Thread Grace
Hello,

I am taking a data analysis class and was given a project. I am having
errors when trying to execute the command. how can I fix this issue? I have
a windows 10.

ERROR: could not open file "C:\Users\Public\Documents\PostgreSQL
10\Documentation\" for reading: No such file or directory HINT: COPY FROM
instructs the PostgreSQL server process to read a file. You may want a
client-side facility such as psql's \copy. SQL state: 58P01


Wonderful PgAdmin

2021-10-25 Thread Paulo Toledo

Hello,
I'm just writing to thank you for the great job you all are doing on 
pgAdmin.

I'm very excited about the ERD tool evolutions.
Congratulations to everyone.

Paulo Alfredo






Re: Problem related to volume creation to pgadmin 4 Docker image

2021-10-25 Thread Dave Page
Hi

Issue created: https://redmine.postgresql.org/issues/6958

On Fri, Oct 22, 2021 at 4:24 PM Rodrigo Mariano 
wrote:

> Hi Dave,
>
> I understand the situation and I believe both options, that you suggested,
> could improve the container.
>
> If you could leave this issue marked on somewhere to be analyzed in the
> future, I thank you so much.
>
> Thank you for your help.
>
> Best regards,
> Rodrigo
> On 22/10/2021 11:31, Dave Page wrote:
>
> Hi
>
> On Fri, Oct 22, 2021 at 3:12 PM Rodrigo Mariano 
> wrote:
>
>> Hi Dave,
>>
>> I tested the ACL command, as you suggested, and it worked when docker
>> container was turned off, but when I lauched pgadmin, it reset the folder
>> permissions again.
>>
> That's very odd - pgAdmin only resets the permission bits. It doesn't have
> any code to touch the ACL.
>
>>
>> Could you consider, in future versions, to give access to host user to
>> */var/lib/pgadmin/storage* folder?
>> For example, other files and folders (e.g. sessions and pgadmin4.db)
>> could be restricted, but storage, as a folder to user files, could have
>> read and execute permissions in order to host user be able to access it.
>>
> That may be safe in your environment, but perhaps not in others (and we
> always aim for secure-by-default). Perhaps a suitable compromise would be
> to either have a config option to avoid the chmod at startup, or to only
> perform it when the directory is first created (so that you can change it
> after first launch, and not have it reset in the future).
>
>>
>> Thank you for your help.
>>
>> Best regards,
>> Rodrigo
>> On 22/10/2021 06:31, Dave Page wrote:
>>
>> Hi
>>
>> On Thu, Oct 21, 2021 at 7:51 PM Rodrigo Mariano 
>> wrote:
>>
>>> Hi Dave,
>>>
>>> Which OS do you use? I'm using Ubuntu 18.
>>>
>> macOS, primarily.
>>
>>>
>>> Nautilus is the file manager to Ubuntu.
>>>
>> Ah, OK.
>>
>>>
>>> I updated my image to dpage/pgadmin4:6.0 in order to avoid old versions.
>>> I add a new volume and I executed the chown command (i.e. sudo chown -R
>>> 5050:5050 ).
>>>
>>> I tried to add my user to 5050 group, but it did not work, because when
>>> pgadmin4 Docker container is executed, it allows just 5050 user to edit the
>>> folder and not other ones from the same group (i.e. *drwx--*).
>>>
>>> *drwx--* is the default permission that pgadmin4 Docker container
>>> gives to volume it creates, in other words, just 5050 user can edit the
>>> volume data, not other ones, even if that user belongs to 5050 group.
>>>
>> OK, now I understand what you mean. Yes, when pgAdmin launches, it'll
>> check the directories it needs, and always tries to fix the permissions to
>> ensure they're secure (i.e. 0700 permissions).
>>
>> You might be able to use the extended ACL to work around that, e.g.
>>
>> setfacl -Rm u:rodrigo:rwX,d:u:rodrigo:rwX 
>>
>> I believe that will recursively give you permissions on the directory on
>> the host (assuming your username is rodrigo), and set it up so permissions
>> are inherited. You may need to ensure your host filesystem is mounted with
>> the 'acl' option.
>>
>>>
>>> Thank you.
>>>
>>> Best regards,
>>> Rodrigo
>>> On 21/10/2021 10:20, Dave Page wrote:
>>>
>>>
>>>
>>> On Thu, Oct 21, 2021 at 1:33 PM Rodrigo Mariano 
>>> wrote:
>>>
 Hi Dave,

 *> I've never needed to do that with plain Docker or Kubernetes. I've
 never used Docker Compose though. *

 Have you ever tried to create a volume to */var/lib/pgadmin/storage*
 folder using newer image versions and you were able to access it via host
 in the nautilus? Using plain Docker.

>>> I have no idea what "the nautilus" is, but yes, I've mapped
>>> /var/lib/pgadmin to the host many times (including 30 seconds ago with
>>> 6.1), and it works fine. As long as appropriate permissions are set on the
>>> directory on the host, I can access it from there as well.
>>>

 If you have, how could I do that?

>>> As you suggested, you could add yourself to the 5050 group, and ensure
>>> the directory on the host is group readable.
>>>

 I did not have this kind of issue with older versions of pgadmin4
 Docker image (e.g. *dpage/pgadmin4:4.15*), this issue has started with
 recent images that I need to change folder permission to 5050:5050 (e.g.
 *dpage/pgadmin4:5.4*).

>>> 4.15 is very old. We've long since had additional checks in pgAdmin to
>>> ensure that we can successfully write to the storage directory, and to stop
>>> running the processes in the container as root that was a) quite dangerous
>>> and b) could allow it to override permissions on the host. In particular,
>>> you're probably hitting the issue mentioned in the callout box at the top
>>> of https://www.pgadmin.org/docs/pgadmin4/6.1/release_notes_4_16.html
>>>
>>>

 Thank you.

 Best regards,
 Rodrigo

 On 21/10/2021 08:36, Dave Page wrote:



 On Thu, Oct 21, 2021 at 12:27 PM Rodrigo Mariano <
 rodmarian...@gmail.com> wrote: