2830
English speaking PostgreSQL public chat. This group is for discussions on PostgreSQL-related topics and strives to provide best-effort support as well.
Immediate Joiner – Power BI Developer | 5+ Years ExperienceH
ello, I am Mohammad Asgar, an experienced Power BI Developer / Data Analyst with over 5 years of expertise in:
Power BI (Advanced Dashboards, Drill-Down, Drill-Through, Storytelling)
SQL, DAX & ETL
Data Modeling
Delivering KPI-driven reports across Telecom, Retail & Manufacturing domains
Delivered enterprise-level dashboards improving decision-making by 10–20%
Proven success in handling large-scale datasets & cloud migrations
Immediate Joiner (within 3–4 days) | Open to Relocate PAN India
LinkedIn: https://www.linkedin.com/in/md-asgar-95425162
9902232976 | asgariitb@gmail.com
Actually, the documentation of PostgreSQL is quite good. I would start there with the topics that are most relevant to your current project.
https://www.postgresql.org/docs/
Aurora postgresql is a database engine made by Amazon that has a "postgresql compatible" interface
Читать полностью…
Hey teams, I have deployed postgres as a docker container on ubuntu linux,
some developer dropped the DB using ddl auto create, is there a way to recover the database?
Was mostly referring to https://www.postgresql.org/docs/current/ddl-schemas.html (you could think of them as subdirectories or namespaces for tables, useful for keeping it clean).
Читать полностью…
That sounds pretty reasonable.
Be aware that your database is still open to any other role ("user") until you REVOKE ALL ON DATABASE ... FROM public;
Really depends on what you want to do, and forgive me if you know all this already and were just concerned about the user aspect.
Читать полностью…
You might want to have a separate schema for them, though, rather than dump their stuff into public. You can set up their search_path to be "$user, public" if it isn't already and it will access public if not found in their own schema.
Читать полностью…
The postgres has good docs... And I would suggest to read them through carefully, at least once, to everyone willing to be a postgres DBA or postgres user...
But that wouldn't be sufficient to be a good DBA. Some experience with less responsibility seems to be required.
(As for MS SQL, but there there are more training courses to begin with).
Another problem is tgat Aurora isn't postgres. While Amazon RDS for Postgres is mostly a closed fork of Postgres, with some rare glitches — the Amazon Aurora definitely isn't.
If you'd be lucky — the AWS team would do most of the work for you.
If you'd not — not a much you could do...
Even though I agree it is not OSS Postgres, it’s not just a Postgres compatible interface service like DSQL or Spanner. Linking this initiative from @mayur555b https://pgscorecard.com/
So ChillBRO I would recommend to first search for ressources on how to master Postgres as a SQL Server DBA and then look at the specificities of Aurora. There are plenty of good stuff out there
But the migration team is saying that Postgres aurora
Читать полностью…
And in our environment we are using SQL Server replication among servers as it’s our business need
Читать полностью…
All…we are in planning to migrate/move from MS Sql to Aurora PostgreSQL, what should I learn and where to start
Читать полностью…
also, next time forbid auto DDL, plan for a proper source control and deployment procedure for DDL scripts
Читать полностью…
ooh i see. that's a thing to keep in mind when i deploy to public;
Читать полностью…
Sorry, I don't really understand what you're saying (it's the first time i'm setting up a postgressql server myself), but based on official documentation here's what i did:
the server OS is Debian, postgresql is installed from official debian repos. upon installation it creates a OS user called postgres. all the postgresql tools and the server processes are started under this user.
i've created PostgreSQL user (not OS user) using createuser command, and a database for that user using createdb command.
next i've added following line to /etc/postgres/17/main/pg_hba.conf
host all all 10.0.2.0/24 scram-sha-256
listen_address=10.0.2.1 to /etc/postgres/17/main/postgresql.conf, so postgres is not accessible from external network at all. the application for this database will be running on the same server, but i need access to the database over the internal network for development
Читать полностью…
It can even be e.g. "$user, viewer" and they are member of a viewer role which has views selecting from public or another app schema rather than public etc. (But, bear in mind you can't actually hide the structure of the database without locking down the system catalog tables which IIRC is not supported.)
Читать полностью…
never mind, found this in official documentation:
PostgreSQL database user names are logically separate from user names of the operating system in which the server runs. If all the users of a particular server also have accounts on the server's machine, it makes sense to assign database user names that match their operating system user names. However, a server that accepts remote connections might have many database users who have no local operating system account, and in such cases there need be no connection between database user names and OS user names.Читать полностью…