GitHub
github.com › porsager › postgres › issues
Issues · porsager/postgres
porsager / postgres Public · Notifications · You must be signed in to change notification settings · Fork 355 · Star 8.7k · Collapse sidebar · Search Issues · is:issue state:open · is:issue state:open Search · LabelsMilestonesNew issueIssue creation is restricted in this repository ·
Author porsager
GitHub
github.com › docker-library › postgres › issues
Issues · docker-library/postgres
docker-library / postgres Public · Notifications · You must be signed in to change notification settings · Fork 1.2k · Star 2.4k · Upgrading between major versions? #37 · roosmaa opened · on Nov 23, 2014 · 127 · Debian Buster is going to cause some reindexing headaches · #582 · tianon opened · on May 17, 2019 · 7 · Search Issues ·
Author docker-library
Why doesn’t PG convert to Git for development?
The Postgres source code is managed in Git: https://git.postgresql.org As for the use of GitHub or similar collaboration platforms (Git <> GitHub!) - that is being discussed on a regular basis on the hackers mailing list. In a nutshell: the Postgres development team wants to stay independent of any external service, so if they did switch the would host something themselves. If you are interested in the discussions, search the mailing list archives. More on reddit.com
24
7
January 23, 2022PostgreSQL database in repository
Usually, you don't store databases in the source control, because each installation/environment of your app is supposed to have it's own data, different from the others. You can and should store SQL scripts to create the structure of your database, such as empty tables, indexes, tables relationships, etc... You can also store scripts that insert the initial data on a newly created database (seed data), such as a default user. If you still want to store the entire database, just find a tool to export it to any text file(s): SQL script, JSON, CSV More on reddit.com
28
34
March 18, 2024Videos
06:34
A Postgres database for every GitHub branch 🤝 GitHub branching ...
#Complete PostgreSQL Guide - Git repository for the ...
- YouTube
19:35
Getting Started with the PostgreSQL Extension for VS Code - YouTube
09:48
New PostgreSQL extension for VS Code with GitHub Copilot Capabilities ...
GitHub
github.com › postgres › postgres
GitHub - postgres/postgres: Mirror of the official PostgreSQL GIT repository. Note that this is just a *mirror* - we don't work with pull requests on github. To contribute, please see https://wiki.postgresql.org/wiki/Submitting_a_Patch · GitHub
Mirror of the official PostgreSQL GIT repository. Note that this is just a *mirror* - we don't work with pull requests on github. To contribute, please see https://wiki.postgresql.org/wiki/Submitting_a_Patch - postgres/postgres
Starred by 21.5K users
Forked by 5.8K users
Languages C 82.9% | PLpgSQL 7.7% | Perl 4.9% | Yacc 1.2% | Meson 0.7% | Makefile 0.6%
GitHub
github.com › brianc › node-postgres › issues
Issues · brianc/node-postgres
LabelsMilestonesNew issue · Open · Closed · Status: Open. #3641 In brianc/node-postgres; · sant123 opened · on Mar 7, 2026 · 9.0 · Status: Open. #3639 In brianc/node-postgres; · brianc opened · on Mar 6, 2026 · · pg@9.0 · 9.0 · Status: Open. #3635 In brianc/node-postgres; ·
Author brianc
GitHub
github.com › pgjdbc › pgjdbc › issues
Issues · pgjdbc/pgjdbc
Postgresql JDBC Driver. Contribute to pgjdbc/pgjdbc development by creating an account on GitHub.
Author pgjdbc
GitHub
github.com › kartotherian › postgres › issues
Issues · kartotherian/postgres
February 14, 2022 - kartotherian / postgres Public archive · Notifications · You must be signed in to change notification settings · Fork 0 · Star 1 · Collapse sidebar · Search Issues · is:issue state:open · is:issue state:open Search · Open · Closed · Try adjusting your search filters.
Author kartotherian
GitHub
github.com › kenhanscombe › project-postgres › issues
Issues · kenhanscombe/project-postgres
kenhanscombe / project-postgres Public · Notifications · You must be signed in to change notification settings · Fork 30 · Star 22 · Collapse sidebar · New issueIssue creation is restricted in this repository · Search Issues · is:issue state:open · is:issue state:open Search ·
Author kenhanscombe
GitHub
github.com › postgres
PostgreSQL · GitHub
June 4, 2026 - Mirror of the official PostgreSQL GIT repository. Note that this is just a *mirror* - we don't work with pull requests on github.
StrongDM
strongdm.com › connect › postgresql-github-issues
PostgreSQL: Integrating into a GitHub Issues workflow
From pgAdmin to DBeaver to OmniDB, as long as the client is capable of connection to PostgreSQL, it will work with StrongDM. ... GitHub Issues is a tracking system built into the GitHub repository.
GitHub
github.com › topics › postgresql
GitHub Topic: PostgreSQL
May 17, 2026 - react python project-planning docker redis django jira bug-tracker postgresql issue-tracker project-management kanban linear gantt boards product-management typescipt vite jira-alternative work-management
Yepcode
yepcode.io › recipes › postgresql-to-github-issues
PostgreSQL to Github issues | YepCode Recipes | Code snippets for solving common problems
Use this template to Read rows from PostgreSQL table using them to create issues in Github repository.
GitHub
github.com › dhamaniasad › awesome-postgres › issues
Issues · dhamaniasad/awesome-postgres
LabelsMilestonesNew issue · Open · Closed · Status: Open. #363 In dhamaniasad/awesome-postgres; · Anastasia-Antonova-retable opened · on Nov 1, 2023 · Status: Open. #352 In dhamaniasad/awesome-postgres; · mizxeren opened · on Jun 22, 2023 · Status: Open.
Author dhamaniasad
Reddit
reddit.com › r/postgresql › why doesn’t pg convert to git for development?
r/PostgreSQL on Reddit: Why doesn’t PG convert to Git for development?
January 23, 2022 -
I simply find it a bit bizarre that in the age of issues, mentions, reactions, branches, CI, MRs/PRs and such, Postgres somehow gets by with email chains and mailing patches around. Am I crazy, or does this sound like a bit of a flaw when even GitHub has been around for a decade and a half.
I mean obviously, it works and it works well. But I certainly feel like a switch would help get the community involved in fixing minor bugs as the barrier to contributing is relatively high now (at least in terms of needing to figure out the unusual process).
Apologies for the somewhat unfitting flair, I’m surprised there’s no “Discussion”
Edit: should have been made clear in the title but I of course meant GitHub/Gitlab style collaboration/workflow tools, not the git command line tool.
Top answer 1 of 5
18
The Postgres source code is managed in Git: https://git.postgresql.org As for the use of GitHub or similar collaboration platforms (Git <> GitHub!) - that is being discussed on a regular basis on the hackers mailing list. In a nutshell: the Postgres development team wants to stay independent of any external service, so if they did switch the would host something themselves. If you are interested in the discussions, search the mailing list archives.
2 of 5
11
Postgres somehow gets by with email chains and mailing patches around. That’s how Linux kernel development works as well. https://en.wikipedia.org/wiki/Linux_kernel#Submitting_code_to_the_kernel does this sound like a bit of a flaw when even GitHub has been around for a decade and a half. Git (and it’s emailing patches model) has pre-dated GitHub for a few years longer. But I certainly feel like a switch would help get the community involved in fixing minor bugs as the barrier to contributing is relatively high now (at least in terms of needing to figure out the unusual process). As someone who doesn’t program in C let alone for the the PostgreSQL project it is possible that: Those who use the current system are more productive in it and their productivity losses wouldn’t be offset by the people who are currently unable to contribute that would join The higher barrier to contribution serves as an effective filter on the quality of contributions No one has simply made the change and convinced the developer community of its merits to get them to go along with the change
GitHub
github.com › CrunchyData › postgres-operator › issues
Issues · CrunchyData/postgres-operator
Community updates for Crunchy Postgres for Kubernetes · #3732 · craigkerstiens opened · on Sep 25, 2023 · 2 · Search Issues · is:issue state:open · is:issue state:open Search · LabelsMilestonesNew issue · Open · Closed · Status: Open. #4453 In CrunchyData/postgres-operator; ·
Author CrunchyData
Medium
medium.com › chrisrbailey › github-actions-using-postgres-postgis-and-psql-e920a2aea7e1
GitHub Actions using Postgres/PostGIS and PSQL | by Chris Bailey | ChrisRBailey | Medium
July 8, 2020 - Additionally, the tests require seeding the database with some GIS data in order for the tests to pass. Most of the issues I had resolved around getting this working. The first hurdle was understanding how to setup Postgres. There were some existing GitHub actions that seemed to do this, but I never got them working.
Stack Overflow
stackoverflow.com › questions › 76788993 › password-authentication-issue-with-postgresql-in-github-actions-python
Password authentication issue with PostgreSQL in GitHub Actions. Python - Stack Overflow
Edit: Also I tried to use postgres as hostname. I got following error: socket.gaierror: [Errno -2] Name or service not known.
GitHub
github.com › Azure › azure-postgresql › issues
Issues · Azure/azure-postgresql
Azure Database for PostgreSQL (fully managed service for PostgreSQL in Azure) - Issues · Azure/azure-postgresql
Author Azure
GitHub
github.com › PostgresApp › PostgresApp › issues
Issues · PostgresApp/PostgresApp
The easiest way to get started with PostgreSQL on the Mac - Issues · PostgresApp/PostgresApp
Author PostgresApp
GitHub
github.com › EnterpriseDB › edb-installers › issues
Issues · EnterpriseDB/edb-installers
PostgreSQL installers packaged by EDB. Contribute to EnterpriseDB/edb-installers development by creating an account on GitHub.
Author EnterpriseDB
Reddit
reddit.com › r/github › postgresql database in repository
r/github on Reddit: PostgreSQL database in repository
March 18, 2024 -
Hi, I’m a beginner at web development so I’m sorry for the dumb question but I recently made a project for a course I’m following that made use of a database I had created in PostgreSQL.
Now, I want to ask, if I want to upload this project on Github, how do I upload the database or the PostgreSQL content I used? What would be the right way of adding a project like that on my Github?
Top answer 1 of 5
29
Usually, you don't store databases in the source control, because each installation/environment of your app is supposed to have it's own data, different from the others. You can and should store SQL scripts to create the structure of your database, such as empty tables, indexes, tables relationships, etc... You can also store scripts that insert the initial data on a newly created database (seed data), such as a default user. If you still want to store the entire database, just find a tool to export it to any text file(s): SQL script, JSON, CSV
2 of 5
29
I'll answer the question instead of telling you not to. Despite what some people are saying here this is a legitimate use case. Many repos will include just the schema of their database instead of the schema and all of the database contents. The schema is used to initialize a local database for tests. Either way for postgres you will want to lookup a tool call pg_dump and pg_restore. These come with most installs of postgres. pg_dump can export all of your database to a SQL file that you can include in your repo like any other file. If you want to go just the schema route - pg_dump has a flag for only exporting the schema as a file. On the opposite.side, you will use pg_restore to load your database back into a postgres instance.