Skip to content

Commit a5ea6ad

Browse files
committed
Beta label and postgres server
1 parent e26fcc7 commit a5ea6ad

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

self-hosting/installation/powersync-service-setup.mdx

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -54,9 +54,9 @@ If you are rolling your own Docker environment, you can include this init script
5454
- 'sleep 10 && mongosh --host mongo:27017 --eval ''try{rs.status().ok && quit(0)} catch {} rs.initiate({_id: "rs0", version: 1, members: [{ _id: 0, host : "mongo:27017" }]})'''
5555
```
5656
57-
### Postgres Storage
57+
### Postgres Storage (Beta)
5858
59-
Postgres can also be used as a storage backend.
59+
Available since version 1.3.8 of [`journeyapps/powersync-service`](https://hub.docker.com/r/journeyapps/powersync-service), you can use Postgres as an alternative storage backend for sync buckets. This feature is currently in [beta](/resources/feature-status).
6060

6161
#### Database Setup
6262

@@ -174,7 +174,7 @@ client_auth:
174174
```
175175

176176
<Info>
177-
**Important:** When using Postgres storage, you must use a separate database instance from your source database used for replication. Using the same database for both purposes may cause unexpected behavior.
177+
**Important:** When using Postgres for sync bucket storage, a separate server is currently required for replication connections (if using Postgres for replication) and storage. Using the same server might cause unexpected results.
178178
</Info>
179179

180180
Specify the connection to Postgres in the `replication` section. Retrieving your database connection string / individual parameters differs by database hosting provider. See [Database Connection](/self-hosting/appendix/database-connection) for further details.

0 commit comments

Comments
 (0)