You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Run this command after replacing <computer-username> with your computer's username:
psql -U <computer-username> postgres < data.dump
This command failed until I did CREATE ROLE <computer-username> WITH LOGIN SUPERUSER PASSWORD <pass>;
In Dbeaver postgres which uses JDBC, it seems JDBC requires a password too, so using the default postgres which has no password would not connect.
So even if students did not create a new ROLE for <computer-username> and used the default postgres user, they would still fail to connect to dbeaver until a password is added with something like ALTER ROLE postgres WITH PASSWORD 'postgres';
The docker method did not have these complexities because the postgres image required the password and created the required roles as the image started.
`
The text was updated successfully, but these errors were encountered:
JDBC، يبدو أن JDBC يتطلب كلمة مرور أيضًا، لذا فإن استخدام postgres الافتراضي الذي لا يحتوي على كلمة مرور لن يؤدي إلى الاتصال.
لذلك حتى لو لم ينشئ الطلاب دورًا جديدًا واستخدموا مستخدم postgres الافتراضي، فسيظلون يفشلون في الاتصال بـ dbeaver حتى تتم إضافة كلمة مرور بشيء مثلALTER ROLE postgres WITH PASSWORD 'postgres';
لم تكن طريقة Docker تحتوي على هذه التعقيدات لأن صورة Postgres تتطلب كلمة المرور وتنشئ الأدوار المطلوبة عند بدء تشغيل الصورة
This command failed until I did
CREATE ROLE <computer-username> WITH LOGIN SUPERUSER PASSWORD <pass>;
In Dbeaver postgres which uses JDBC, it seems JDBC requires a password too, so using the default postgres which has no password would not connect.
So even if students did not create a new ROLE for
<computer-username>
and used the default postgres user, they would still fail to connect to dbeaver until a password is added with something likeALTER ROLE postgres WITH PASSWORD 'postgres';
The docker method did not have these complexities because the postgres image required the password and created the required roles as the image started.
`
The text was updated successfully, but these errors were encountered: