> For the complete documentation index, see [llms.txt](https://docs.postgresql.tw/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.postgresql.tw/appendixes/h.-wai-bu-zhuan-an/h.1.-yong-hu-duan-jie-mian.md).

# H.1. 用戶端介面

There are only two client interfaces included in the base PostgreSQL distribution:

* [libpq](https://www.postgresql.org/docs/10/static/libpq.html) is included because it is the primary C language interface, and because many other client interfaces are built on top of it.
* [ECPG](https://www.postgresql.org/docs/10/static/ecpg.html) is included because it depends on the server-side SQL grammar, and is therefore sensitive to changes in PostgreSQL itself.

All other language interfaces are external projects and are distributed separately. [Table H.1](https://www.postgresql.org/docs/10/static/external-interfaces.html#LANGUAGE-INTERFACE-TABLE) includes a list of some of these projects. Note that some of these packages might not be released under the same license as PostgreSQL. For more information on each language interface, including licensing terms, refer to its website and documentation.

**Table H.1. Externally Maintained Client Interfaces**

| Name          | Language   | Comments                             | Website                                    |
| ------------- | ---------- | ------------------------------------ | ------------------------------------------ |
| DBD::Pg       | Perl       | Perl DBI driver                      | <http://search.cpan.org/dist/DBD-Pg/>      |
| JDBC          | Java       | Type 4 JDBC driver                   | <https://jdbc.postgresql.org/>             |
| libpqxx       | C++        | New-style C++ interface              | <http://pqxx.org/>                         |
| node-postgres | JavaScript | Node.js driver                       | <https://node-postgres.com/>               |
| Npgsql        | .NET       | .NET data provider                   | <http://www.npgsql.org/>                   |
| pgtcl         | Tcl        |                                      | <https://github.com/flightaware/Pgtcl>     |
| pgtclng       | Tcl        |                                      | <http://sourceforge.net/projects/pgtclng/> |
| pq            | Go         | Pure Go driver for Go's database/sql | <https://github.com/lib/pq>                |
| psqlODBC      | ODBC       | ODBC driver                          | <https://odbc.postgresql.org/>             |
| psycopg       | Python     | DB API 2.0-compliant                 | <http://initd.org/psycopg/>                |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.postgresql.tw/appendixes/h.-wai-bu-zhuan-an/h.1.-yong-hu-duan-jie-mian.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
