PostgreSQL Wiki
wiki.postgresql.org › wiki › Working_with_Git
Working with Git - PostgreSQL wiki
December 23, 2024 - If you develop a feature over a longer period of time, you want to allow for intermediate review. The traditional approach to that has been emailing huge patches around. The more advanced approach that we want to try (see also Peter Eisentraut's blog entry) is that you push your Git branches to a private area on git.postgresql.org, where others can pull your work, operate on it using the familiar Git tools, and perhaps even send you improvements as Git-formatted patches.
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%
Source control for PostgreSql Data base with git - Stack Overflow
I have a PostgreSql Data base, and I want to keep the schema in source control. I prefer using git because all of my code is in git. Is there a way to accomplish that. Thanks ... Save this answer. ... Show activity on this post. Generally the modern approach to doing this these days is to learn to use propel ORM or Doctrine ORM, which will version your database for ... More on stackoverflow.com
PostgreSQL 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, 2024How can I put a database under git (version control)? - Stack Overflow
Though this does not answer how ... aim of making the database work like git, meaning all your data is branchable, time-travellable and auditable. Personally, I think TerminusDB is the most promising one. ... Migra (diffing for Postgres schemas/data.... More on stackoverflow.com
Version control for a postgres db's user defined functions?
23
12
August 15, 2019Andrew Nesbitt
nesbitt.io › 2026 › 02 › 26 › git-in-postgres.html
Git in Postgres | Andrew Nesbitt
February 26, 2026 - An object’s OID is computed the same way git does it, SHA1("<type> <size>\0<content>"), using pgcrypto’s digest() function, and refs get compare-and-swap updates through SELECT FOR UPDATE. A libgit2 backend registers these tables as its storage layer, and if the protocol really is separable from the format, a normal git client should be able to push to and clone from a Postgres database without knowing the difference.
PostgreSQL
postgresql.org › docs › current › git.html
PostgreSQL: Documentation: 18: I.1. Getting the Source via Git
May 14, 2026 - I.1. Getting the Source via Git # With Git you will make a copy of the entire code repository on your …
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.
Lobsters
lobste.rs › s › ibkc72 › git_postgres
Git in Postgres | Lobsters
February 26, 2026 - Yes, we should build this into the database with version numbers etc. but it feels like such a common problem that there should be a generic data-type for this. Storing git objects in postgres is probably overkill for this specific use case but I have considered it.
Medium
patriciaosifo.medium.com › getting-started-with-postgresql-16-on-git-bash-9b83d87f3589
Getting Started with PostgreSQL 16 on Git Bash | by Patricia Atiti Osifo-Iduorobo | Medium
October 18, 2023 - If successful, PgAdmin4, PostgreSQL 16 (or whatever is the latest version), etc. will all be available in a Folder for you. ... You can also always use these commands in the Git Bash terminal: which psql OR postgres --version to check for the version and location of psql or the version of the Postgres respectively.
pgPedia
pgpedia.info › g › GIT.html
GIT - pgPedia - a PostgreSQL Encyclopedia
Online tools for PostgreSQL ... code management system used to manage the PostgreSQL source code. GIT is the revision control / source code management (SCM) system used to manage PostgreSQL's source code....
Top answer 1 of 3
1
Generally the modern approach to doing this these days is to learn to use propel ORM or Doctrine ORM, which will version your database for you and keep the structure in sync as you commit the basic schema (in an xml format) and migrations.
PHP ORMs: Doctrine vs. Propel Has more about propel vs. doctrine.
2 of 3
1
You can use some tool that can generate text representation of db schema into files in some folder under vcs.
To see adequate working tree status you'll need to run schema generation before git status.
Before update from remote (git fetch && git rebase or git pull) you'll need to get db schema into worktree.
If that version differs from latest version in HEAD then you'll need to revert it in db or commit.
After update you'll need to get db schema into worktree again, check out diff and revert it in real db until db schema get will produce clean worktree.
P.S. I'm using this technique for MsSql db schemas in git. I even added db data to repo, this may be useful too.
PostgreSQL Wiki
wiki.postgresql.org › wiki › Committing_with_Git
Committing with Git - PostgreSQL wiki
May 23, 2025 - (If your user name and/or email are configured globally, you need not configure them again for each new repository.) With this approach, the REL9_0_STABLE repository will pull from and push to the local postgresql repository, which in turn will pull from and push to the master server. Thus, you must do this to update (supposing both repositories are in your home directory): cd ~/postgresql.git git fetch cd ~/REL9_0_STABLE git pull
PostgreSQL
postgresql.org › docs › 9.1 › git.html
PostgreSQL: Documentation: 9.1: Getting The Source via Git
October 11, 2021 - git clone http://git.postgresql.org/git/postgresql.git · The HTTP protocol is less efficient than the Git protocol, so it will be slower to use. Whenever you want to get the latest updates in the system, cd into the repository, and run: ... Git can do a lot more things than just fetch the source. For more information, consult the Git man pages, or see the website at http://git-scm.com.
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.
Top answer 1 of 16
167
Take a database dump, and version control that instead. This way it is a flat text file.
Personally I suggest that you keep both a data dump, and a schema dump. This way using diff it becomes fairly easy to see what changed in the schema from revision to revision.
If you are making big changes, you should have a secondary database that you make the new schema changes to and not touch the old one since as you said you are making a branch.
2 of 16
34
I'm starting to think of a really simple solution, don't know why I didn't think of it before!!
- Duplicate the database, (both the schema and the data).
- In the branch for the new-major-changes, simply change the project configuration to use the new duplicate database.
This way I can switch branches without worrying about database schema changes.
EDIT:
By duplicate, I mean create another database with a different name (like my_db_2); not doing a dump or anything like that.
Postgresql
git.postgresql.org › gitweb
git.postgresql.org Git
It serves mirrors of selected projects as Git pull and web access, and it offers project hosting with push access as well as user branch hosting. You can find more user branches at the postgres organization account on Github. This repository also contains the public repository for PostgreSQL itself.
PostgreSQL
postgresql.org › docs › 15 › git.html
PostgreSQL: Documentation: 15: I.1. Getting the Source via Git
May 14, 2026 - git clone https://git.postgresql.org/git/postgresql.git
PostgreSQL
postgresql.org › docs › current › sourcerepo.html
PostgreSQL: Documentation: 18: Appendix I. The Source Code Repository
May 14, 2026 - The PostgreSQL source code is stored and managed using the Git version control system.
Postgres Professional
postgrespro.com › docs › postgresql › 16 › git
PostgreSQL : Documentation: 16: I.1. Getting the Source via Git : Postgres Professional
git clone https://git.postgresql.org/git/postgresql.git
Pgcon
pgcon.org › 2010 › schedule › attachments › 162_pg-git.pdf pdf
Using Git with PostgreSQL Andrew Dunstan andrew@dunslane.net
Switching_PostgreSQL_from_CVS_to_Git · CVS work pattern – developer · ●cvs checkout pgsql · ●Repeat till done: – Work · – Test · – Occasionally cvs update · ●Hope it doesn't blow up your work · ●If it does, fix it by hand · CVS developer problems · ●Can't branch · ●Can't easily checkpoint code or roll it back · ●No merge support to speak of · ●Have to fool cvs about added files for patch ·
InfoQ
infoq.com › news › 2023 › 11 › DoltgreSQL-git-for-data-postgres
Git-for-Data, Version-Controlled Database Dolt Gets PostgreSQL-Flavor - InfoQ
November 25, 2023 - DoltgreSQL builds on top of the version-controlled database Dolt to provide Git-like log, diff, branch, and merge functionality for your Postgres database schema and data.
PostgreSQL
postgresql.org › docs › 8.1 › sourcerepo.html
PostgreSQL: Documentation: 8.1: The Source Code Repository
January 1, 2012 - Note that building PostgreSQL from the source repository requires reasonably up-to-date versions of bison, flex, and Perl. These tools are not needed to build from a distribution tarball since the files they are used to build are included in the tarball. Other tool requirements are the same as shown in Chapter 14. With Git you will make a copy of the entire code repository on your local machine, so you will have access to all history and branches offline.