| From: | David Steele <david(at)pgmasters(dot)net> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, David Fetter <david(at)fetter(dot)org>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: WIP: document the hook system |
| Date: | 2021-03-04 16:22:48 |
| Message-ID: | d6456d89-1e5a-10ad-cc61-3fcc0d4144bd@pgmasters.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 3/4/21 10:00 AM, Peter Eisentraut wrote:
> On 15.01.21 08:28, Peter Eisentraut wrote:
>> On 2020-12-31 04:28, David Fetter wrote:
>>> This could probably use a lot of filling in, but having it in the
>>> actual documentation beats needing to know folklore even to know
>>> that the capability is there.
>>
>> This patch seems quite short of a state where one could begin to
>> evaluate it. Documenting the hooks better seems a worthwhile goal.
>> I think the question is whether we can develop documentation that is
>> genuinely useful by itself without studying the relevant source code.
>> This submission does not address that question.
>
> There hasn't been any meaningful progress on this, and no new patch to
> look at, so I'm proposing to set this as returned with feedback.
+1. I'll close it on March 9 unless there are objections.
Regards,
--
-David
david(at)pgmasters(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Pryzby | 2021-03-04 16:29:12 | Re: Improvements and additions to COPY progress reporting |
| Previous Message | Matthias van de Meent | 2021-03-04 16:19:18 | Re: Improvements and additions to COPY progress reporting |