106 lines
3.1 KiB
Plaintext
106 lines
3.1 KiB
Plaintext
export const metadata = {
|
|
title: `PostgreSQL Locking Module Provider`,
|
|
}
|
|
|
|
# {metadata.title}
|
|
|
|
The PostgreSQL Locking Module Provider uses PostgreSQL's advisory locks to control and manage locks across multiple instances of Medusa. Advisory locks are lightweight locks that do not interfere with other database transactions. By using PostgreSQL's advisory locks, Medusa can create distributed locks directly through the database.
|
|
|
|
The provider uses the existing PostgreSQL database in your application to manage locks, so you don't need to set up a separate database or service to manage locks.
|
|
|
|
<Note>
|
|
|
|
While this provider is suitable for production environments, it's recommended to use the [Redis Locking Module Provider](../redis/page.mdx) if possible.
|
|
|
|
</Note>
|
|
|
|
---
|
|
|
|
## Register the PostgreSQL Locking Module Provider
|
|
|
|
To register the PostgreSQL Locking Module Provider, add it to the list of providers of the Locking Module in `medusa-config.ts`:
|
|
|
|
```ts title="medusa-config.ts"
|
|
module.exports = defineConfig({
|
|
// ...
|
|
modules: [
|
|
{
|
|
resolve: "@medusajs/medusa/locking",
|
|
options: {
|
|
providers: [
|
|
{
|
|
resolve: "@medusajs/medusa/locking-postgres",
|
|
id: "locking-postgres",
|
|
// set this if you want this provider to be used by default
|
|
// and you have other Locking Module Providers registered.
|
|
is_default: true,
|
|
},
|
|
],
|
|
},
|
|
},
|
|
],
|
|
})
|
|
```
|
|
|
|
### Run Migrations
|
|
|
|
The PostgreSQL Locking Module Provider requires a new `locking` table in the database to store the locks. So, you must run the migrations after registering the provider:
|
|
|
|
```bash
|
|
npx medusa db:migrate
|
|
```
|
|
|
|
This will run the migration in the PostgreSQL Locking Module Provider and create the necessary table in the database.
|
|
|
|
---
|
|
|
|
## Use Provider with Locking Module
|
|
|
|
The PostgreSQL Locking Module Provider will be the default provider if you don't register any other providers, or if you set the `is_default` flag to `true`:
|
|
|
|
export const defaultHighlights = [
|
|
["11", "is_default"]
|
|
]
|
|
|
|
```ts title="medusa-config.ts" highlights={defaultHighlights}
|
|
module.exports = defineConfig({
|
|
// ...
|
|
modules: [
|
|
{
|
|
resolve: "@medusajs/medusa/locking",
|
|
options: {
|
|
providers: [
|
|
{
|
|
resolve: "@medusajs/medusa/locking-postgres",
|
|
id: "locking-postgres",
|
|
is_default: true,
|
|
},
|
|
],
|
|
},
|
|
},
|
|
],
|
|
})
|
|
```
|
|
|
|
If you use the Locking Module in your customizations, the PostgreSQL Locking Module Provider will be used by default in this case. You can also explicitly use this provider by passing its identifier `lp_locking-postgres` to the Locking Module's service methods.
|
|
|
|
For example, when using the `acquire` method in a [workflow step](!docs!/learn/fundamentals/workflows):
|
|
|
|
```ts
|
|
import { Modules } from "@medusajs/framework/utils"
|
|
import { createStep } from "@medusajs/framework/workflows-sdk"
|
|
|
|
const step1 = createStep(
|
|
"step-1",
|
|
async ({}, { container }) => {
|
|
const lockingModuleService = container.resolve(
|
|
Modules.LOCKING
|
|
)
|
|
|
|
await lockingModuleService.acquire("prod_123", {
|
|
provider: "lp_locking-postgres",
|
|
})
|
|
}
|
|
)
|
|
```
|