[GRASS-user] increase sqlite performance

[Luí­s Moreira de Sousa]

Hi again Iván,

basically you create a new mapset and set the back-end to Postgres with db.connect [0]. Then use g.copy [1] to add in the maps you need in the new mapset.

Since you have a load of RAM available, you may also experiment creating a new mapset with a SQLite database in memory. Just mind its volatile nature, you will need to copy any relevant results to another mapset with a persistent back-end.

Hope this helps. Regards.

[0] https://grass.osgeo.org/grass-stable/manuals/db.connect.html

[1] https://grass.osgeo.org/grass-stable/manuals/g.copy.html
--
Luís Moreira de Sousa
Mastodon: https://mastodon.social/@luis_de_sousa
URL: https://ldesousa.codeberg.page

Sent with Proton Mail secure email.

On Tuesday, 21 January 2025 at 09:13, Ivan Marchesini via grass-user <grass-user at lists.osgeo.org> wrote:

> Hi Luis
> 
> thank you for your reply
> 
> I totally agree with you but unfortunately recently I was involved in an
> already-running project where data have been stored using sqlite
> 
> DO you have any suggestion on how to smoothly move all the sqlite
> database into postgresql?
> 
> thank you
> 
> regards
> 
> 
> On 21/01/25 08:52, Luí s Moreira de Sousa wrote:
> 
> > Dear Ivan,
> > 
> > I have worked with GRASS in similar circumstances. The best advice I can offer is to replace SQLite with Postgres. As you load up on the number of features and raster size, data-base exceptions and halts become increasingly frequent and increasingly harder to address.
> > 
> > Also, beware of parallel access to SQLite.
> > 
> > Regards.
> 
> _______________________________________________
> grass-user mailing list
> grass-user at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user