Availability
The PostgreSQL connector is available under SOCK → Sources → Add source → Connect System. It supports PostgreSQL 15 and is certified through 16.
| Property | Current behaviour |
|---|---|
| Execution | Desktop |
| Identity | The signed-in member's database credential |
| Secret storage | Operating-system credential store, scoped to the member |
| Direction | Read-only; MSOCK writes nothing to PostgreSQL |
| Bounded read cap | 10,000 rows |
| Sample cap | 200 rows |
Connection fields
| Field | Requirement or default |
|---|---|
| Host | Required |
| Port | 5432 by default |
| Database | Required |
| User | Required |
| Password | Secret |
| SSL mode | require by default; verify-ca, verify-full, or disable |
| TLS verification | Available with the selected SSL mode |
Keep require or a verification mode unless your approved local environment explicitly requires otherwise. verify-full provides the strongest identity check when the certificate and host name are configured correctly.
Select the evidence scope
After the connection succeeds, browse the accessible database, schemas, and tables. Select only the structures needed for the harness and decide whether bounded samples are appropriate for the data classification.
MSOCK can read schemas, tables, keys, views, indexes, routines, sequences, triggers, row counts, grants, and bounded samples, subject to database permissions and engine support.
Version and driver checks
A server below PostgreSQL 15 is refused before harness files are written. A server above the certified range can be captured, but the manifest records an uncertified-version warning. If the required driver is unavailable, the connector reports that condition and tells you to repair the local prerequisite before retrying.