# Gramps with PostgreSQL : multi-user use?

**URL:** <https://gramps.discourse.group/t/gramps-with-postgresql-multi-user-use/8013>\
**Category:** Development\
**Created:** [July 29, 2025, 9:27am UTC](https://gramps.discourse.group/t/gramps-with-postgresql-multi-user-use/8013 "2025-07-29T09:27:18Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![emyoulation](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/emyoulation/32/67_2.png) [@emyoulation](https://gramps.discourse.group/u/emyoulation)\
**Post date:** [July 29, 2025, 12:11pm UTC](https://gramps.discourse.group/t/gramps-with-postgresql-multi-user-use/8013/2 "2025-07-29T12:11:16Z")

</div>

The database backend is not where the Gramps (for desktops) single-user limitation is implemented.

See the discussion at

> [@Should the Plugin Registration fail gracefully for missing Prerequisites?](https://gramps.discourse.group/t/should-the-plugin-registration-fail-gracefully-for-missing-prerequisites/5147/13):
>
> Hopefully we can allow multi-user access to any backend. The reason for the single-user restriction was to improve the performance of the BSDDB database. If the \_create\_undo\_manager approach doesn’t work then I am open to consider alternatives. It may also be time to have another look at storing objects as JSON rather than pickled blobs. I’ll release v5.2.1 over the weekend. After that, I’ll have time to start thinking about v5.3.

---

_[View the full topic](https://gramps.discourse.group/t/gramps-with-postgresql-multi-user-use/8013)._