zhukang 1c7abd81d1 All 310 Manus skill-hub community skills as a Kortix marketplace registry

- 310 registry:skill items, 1528 files, 7 categories (hub tags)
- registry.json generated by @kortix/registry buildRegistry
- nested SKILL.md in sn-da-* renamed SUBSKILL.md (no phantom skills)
- provenance + licenses: SOURCES.md

2026-09-15 13:37:20 +08:00

1.6 KiB

Raw Blame History

title	description	tags
PlanetScale Postgres Connections	Connection guide for PlanetScale Postgres	planetscale, postgres, connections, ssl, troubleshooting

PlanetScale Postgres Connections

Postgres docs: https://planetscale.com/docs/postgres/connecting

Protocol	Standard Port	Pooled Port	SSL
Postgres	5432	6432 (PgBouncer)	Required

Credentials (roles) are branch-specific and cannot be recovered after creation.

Connection String

postgresql://<user>:<password>@<host>.horizon.psdb.cloud:5432/<database>?sslmode=verify-full&sslrootcert=system&sslnegotiation=direct

Use port 6432 for PgBouncer (applications/OLTP). Use port 5432 for DDL, admin tasks, and migrations.

Troubleshooting

Error	Fix
`password authentication failed`	Check role format: `<role>.<branch_id>`
`too many clients already`	Use PgBouncer (port 6432)
`SSL connection is required`	Add `sslmode=verify-full&sslrootcert=system`

Best practices:

Use the PlanetScale Postgres metrics page to monitor direct and PgBouncer connections
Route OLTP traffic to port 6432 and reserve 5432 for admin/migrations.
Run maintenance that changes session state (e.g. SET default_transaction_read_only) on port 5432 only. On 6432 (PgBouncer transaction pooling) session SETs leak into other clients' connections.
Avoid raising max_connections reactively instead of pooling.

1.6 KiB Raw Blame History

PlanetScale Postgres Connections

Connection String

Troubleshooting

1.6 KiB

Raw Blame History