> 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/15/client-interfaces/ecpg-embedded-sql-in-c/35.14.-embedded-sql-commands/ecpg-sql-allocate-descriptor.md).

# ALLOCATE DESCRIPTOR

## ALLOCATE DESCRIPTOR

ALLOCATE DESCRIPTOR — 配置 SQL 描述區

### 語法

```

ALLOCATE DESCRIPTOR name
```

### 說明

`ALLOCATE DESCRIPTOR` 配置新的具名 SQL 描述區，可用於 PostgreSQL 伺服器與主機程式之間交換資料。

使用完畢後，應使用 `DEALLOCATE DESCRIPTOR` 命令釋放描述區。

### 參數

*`name`*

SQL 描述區的名稱，區分大小寫。可以是 SQL 識別字或主機變數。

### 範例

```

EXEC SQL ALLOCATE DESCRIPTOR mydesc;
```

### 相容性

SQL 標準規定了 `ALLOCATE DESCRIPTOR`。

### 另請參閱

[DEALLOCATE DESCRIPTOR](/15/client-interfaces/ecpg-embedded-sql-in-c/35.14.-embedded-sql-commands/ecpg-sql-deallocate-descriptor.md), [GET DESCRIPTOR](/15/client-interfaces/ecpg-embedded-sql-in-c/35.14.-embedded-sql-commands/ecpg-sql-get-descriptor.md), [SET DESCRIPTOR](/15/client-interfaces/ecpg-embedded-sql-in-c/35.14.-embedded-sql-commands/ecpg-sql-set-descriptor.md)

***

原文：[PostgreSQL 15.19 Documentation](https://www.postgresql.org/docs/15/ecpg-sql-allocate-descriptor.html)


---

# 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/15/client-interfaces/ecpg-embedded-sql-in-c/35.14.-embedded-sql-commands/ecpg-sql-allocate-descriptor.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.