Forked from GraphQLCollege/graphql-postgres-subscriptions, where we replaced `pg-ipc` with `pg-listen` so that the database connection with retry and reconnect.
npm install @originlabs/graphql-postgres-subscriptions-retryForked from GraphQLCollege/graphql-postgres-subscriptions, where we replaced pg-ipc with pg-listen so that the database connection with retry and reconnect.
A graphql subscriptions implementation using postgres and apollo's graphql-subscriptions.
This package implements the PubSubEngine Interface from the graphql-subscriptions package and also the new AsyncIterator interface. It allows you to connect your subscriptions manger to a postgres based Pub Sub mechanism to support multiple subscription manager instances.
yarn add @originlabs/graphql-postgres-subscriptions-retry or npm install @originlabs/graphql-postgres-subscriptions-retry --save
Example app: https://github.com/GraphQLCollege/apollo-subscriptions-example
First of all, follow the instructions in graphql-subscriptions to add subscriptions to your app.
Afterwards replace PubSub with PostgresPubSub:
``js
// Before
import { PubSub } from "graphql-subscriptions-retry";
export const pubsub = new PubSub();
`
`js
// After
import { PostgresPubSub } from "graphql-postgres-subscriptions-retry";
export const pubsub = new PostgresPubSub();
await pubsub.connect()
`
Don't forget to await the connect() method, or else it will never start the connection with postgres.
This library uses pg-listen to connect to PostgreSQL. If you want to customize connection options, please refer to their connection docs.
You have two options:
If you don's send any argument to new PostgresPubSub(), we'll create a postgres client with no arguments.
You can also pass node-postgres connection options to PostgresPubSub.
Important: If you want to use the asyncIterator (which is used by graphql subscriptions) you need to pass them as an array of topics on the options parameter. This should be an array of all the topics/channels you want to subscribe to. The reason we need to know these ahead of time, is because otherwise it would be an async operation to add them or create the async iterator or use the asyncIteratorPromised function instead.
`js`
export const pubsub = new PostgresPubSub({
topics: ['a', 'b', 'c']
})
await pubsub.connect()
The second argument to new PostgresPubSub() is the commonMessageHandler. The common message handler gets called with the received message from PostgreSQL.
You can transform the message before it is passed to the individual filter/resolver methods of the subscribers.
This way it is for example possible to inject one instance of a DataLoader which can be used in all filter/resolver methods.
`javascript`
const getDataLoader = () => new DataLoader(...)
const commonMessageHandler = ({attributes: {id}, data}) => ({id, dataLoader: getDataLoader()})
const pubsub = new PostgresPubSub({ client, commonMessageHandler });
`javascript`
export const resolvers = {
Subscription: {
somethingChanged: {
resolve: ({ id, dataLoader }) => dataLoader.load(id)
}
}
};
Following how pg-listen works, PostgresPubSub instances have an events event emitter which emits 'error' events.
`js
const ps = new PostgresPubSub();
ps.events.on("error", err => {
console.log(err)
})
`Shutdown
This fork provides a new async close():Promise method that can be called to stop the listeners and release the pg connection for a clean shutdown.
This project has an integration test suite that uses jest to make sure everything works correctly.
Run tests via docker compose:
docker compose build