---
title: "Discussion on \"Native Postgres, PGlite, or In-Memory? Choosing a Postgres Engine for Local Supabase Development\" | Hashnode"
description: "Discussion on \"Native Postgres, PGlite, or In-Memory? Choosing a Postgres Engine for Local Supabase Development\". Three ways to run the database under a local Supabase backend, what each is good at, and the trade-offs the benchmarks don't show"
url: "https://hashnode.com/posts/native-postgres-pglite-or-in-memory-choosing-a-postgres-engine-for-local-supabase-development/6ad0be75167952425f510f60"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Native Postgres, PGlite, or In-Memory? Choosing a Postgres Engine for Local Supabase Development](https://lucalucas.hashnode.dev/native-postgres-pglite-or-in-memory-choosing-a-postgres-engine-for-local-supabase-development?utm_source=hashnode&utm_medium=feed)

Three ways to run the database under a local Supabase backend, what each is good at, and the trade-offs the benchmarks don't show

Oct 15 · 7 min read · lucalucas.hashnode.dev  
Read the article

-   [#postgresql](https://hashnode.com/tag/postgresql)
-   [#supabase](https://hashnode.com/tag/supabase)
-   [#pglite](https://hashnode.com/tag/pglite)
-   [#testing](https://hashnode.com/tag/testing)
-   [#webdev](https://hashnode.com/tag/webdev)

## Written by

[Lucas Martin](https://hashnode.com/@lucasmart)

@lucasmart · Bengaluru, India

  
[View profile](https://hashnode.com/@lucasmart)

Designing with intention. Moving with precision. | Motion & Graphic Designer.

Designing with intention. Moving with precision. | Motion &amp; Graphic Designer.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
