| From: | Amit Langote <amitlangote09(at)gmail(dot)com> |
|---|---|
| To: | "pgsql-docs(at)postgresql(dot)org" <pgsql-docs(at)postgresql(dot)org> |
| Subject: | Link section in custom scan documentation |
| Date: | 2015-05-15 07:22:42 |
| Message-ID: | CA+HiwqHaXWcc+2hg1fjLsi+PE7tK-hX_2eLY7vTKGx93E=8yBQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
Hi,
I propose attached which does:
the <function>BeginCustomScan</> callback will be invoked to give the
- custom scan provider a chance to do whatever else is needed.
+ custom scan provider a chance to do whatever else is needed. See
+ <xref linkend="custom-scan-execution"> for more details.
It would be similar to how it's done elsewhere in custom-scan.sgml like:
Convert a custom path to a finished plan. The return value will generally
be a <literal>CustomScan</> object, which the callback must allocate and
initialize. See <xref linkend="custom-scan-plan"> for more details.
Thanks,
Amit
| Attachment | Content-Type | Size |
|---|---|---|
| custom-scan-link-section.patch | application/octet-stream | 699 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2015-05-16 12:37:59 | Update docs for GIN index improvements |
| Previous Message | Bruce Momjian | 2015-05-11 16:05:18 | Re: Add a new table for Transaction Isolation? |