npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2025 – Pkg Stats / Ryan Hefner

@powersync/service-module-postgres-storage

v0.10.16

Published

This module provides a `BucketStorageProvider` which uses a Postgres database for persistence.

Readme

Postgres Sync Bucket Storage

This module provides a BucketStorageProvider which uses a Postgres database for persistence.

Configuration

Postgres storage can be enabled by selecting the appropriate storage type and providing connection details for a Postgres server.

The storage connection configuration supports the same fields as the Postgres replication connection configuration.

A sample YAML configuration could look like

replication:
  # Specify database connection details
  # Note only 1 connection is currently supported
  # Multiple connection support is on the roadmap
  connections:
    - type: postgresql
      uri: !env PS_DATA_SOURCE_URI

# Connection settings for sync bucket storage
storage:
  type: postgresql
  # This accepts the same parameters as a Postgres replication source connection
  uri: !env PS_STORAGE_SOURCE_URI

IMPORTANT:

Separate Postgres servers are required for replication connections if using PostgreSQL versions below 14.

| PostgreSQL Version | Server configuration | | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Below 14 | Separate servers are required for the source and sync bucket storage. Replication will be blocked if the same server is detected. | | 14 and above | The source database and sync bucket storage database can be on the same server. Using the same database (with separate schemas) is supported but may lead to higher CPU usage. Using separate servers remains an option. |

Connection credentials

The Postgres bucket storage implementation requires write access to the provided Postgres database. The module will create a powersync schema in the provided database which will contain all the tables and data used for bucket storage. Ensure that the provided credentials specified in the uri or username, password configuration fields have the appropriate write access.

A sample user could be created with the following

If a powersync schema should be created manually

CREATE USER powersync_storage_user
WITH
  PASSWORD 'secure_password';

CREATE SCHEMA IF NOT EXISTS powersync AUTHORIZATION powersync_storage_user;

GRANT CONNECT ON DATABASE postgres TO powersync_storage_user;

GRANT USAGE ON SCHEMA powersync TO powersync_storage_user;

GRANT ALL PRIVILEGES ON ALL TABLES IN SCHEMA powersync TO powersync_storage_user;

If the PowerSync service should create a powersync schema

CREATE USER powersync_storage_user
WITH
  PASSWORD 'secure_password';

-- The user should only have access to the schema it created
GRANT CREATE ON DATABASE postgres TO powersync_storage_user;