# Enhanced PostgreSQL Addon Submitted

**URL:** <https://gramps.discourse.group/t/enhanced-postgresql-addon-submitted/8083>\
**Category:** Development\
**Tags:** third-party-addon\
**Created:** [August 6, 2025, 4:38pm UTC](https://gramps.discourse.group/t/enhanced-postgresql-addon-submitted/8083 "2025-08-06T16:38:53Z")\
**Posts on this page:** 1\
**Showing post:** 36

<div class="post-metadata">

**Author:** ![UlrichDemlehner](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/ulrichdemlehner/32/2482_2.png) [@UlrichDemlehner](https://gramps.discourse.group/u/UlrichDemlehner)\
**Post date:** [December 19, 2025, 6:41pm UTC](https://gramps.discourse.group/t/enhanced-postgresql-addon-submitted/8083/36 "2025-12-19T18:41:30Z")

</div>

> [@dsblank](#):
>
> What issues did you have specifically with Gramps 6 + SQLite and large trees? Was it the import, using specific filters, views, etc?

I described it here on the forum in some detail with quantitative performance measurements some time ago. If I remember correctly you also where a part of that discussion. Ah, found it: [Performance Issues with Gramps - #16 by UlrichDemlehner](https://gramps.discourse.group/t/performance-issues-with-gramps/5350/16)

Basically the main point is that searches in the person and event views are just too slow and using SQLite as database backend in v6 doubles the time searches need compared with v5.1.6 on BSDDB. This is completely independent of using RegEx searches or “normal” ones. The other views are ok but those have entries in the range up to 10k or so and that has never been a problem with Gramps.

---

_[View the full topic](https://gramps.discourse.group/t/enhanced-postgresql-addon-submitted/8083)._