Tom Lane wrote:
Simon Riggs <[EMAIL PROTECTED]> writes:
On Sun, 2007-12-16 at 07:58 -0800, Joshua D. Drake wrote:
Bruce Momjian wrote:
I think these are
documented-in-the-source-code type issues.
If they are an API they need to be documented. Code is poor (even well
documented code) substitut
Simon Riggs <[EMAIL PROTECTED]> writes:
> On Sun, 2007-12-16 at 07:58 -0800, Joshua D. Drake wrote:
>> Bruce Momjian wrote:
>>> I think these are
>>> documented-in-the-source-code type issues.
>>
>> If they are an API they need to be documented. Code is poor (even well
>> documented code) substit
On Sun, 2007-12-16 at 07:58 -0800, Joshua D. Drake wrote:
> Bruce Momjian wrote:
> > Simon Riggs wrote:
> >> Looks like we need some docs on all these new plugin APIs we've
> >> introduced in this release.
> >>
> >> - PL/pgSQL hooks
> >> - planner hooks
> >> - join order hooks
> >
> > Do we normal
Bruce Momjian wrote:
Simon Riggs wrote:
Looks like we need some docs on all these new plugin APIs we've
introduced in this release.
- PL/pgSQL hooks
- planner hooks
- join order hooks
Do we normally document these? I think these are
documented-in-the-source-code type issues.
If they are a
Simon Riggs wrote:
> Looks like we need some docs on all these new plugin APIs we've
> introduced in this release.
>
> - PL/pgSQL hooks
> - planner hooks
> - join order hooks
Do we normally document these? I think these are
documented-in-the-source-code type issues.
--
Bruce Momjian <[EMAI
Looks like we need some docs on all these new plugin APIs we've
introduced in this release.
- PL/pgSQL hooks
- planner hooks
- join order hooks
Thanks,
--
Simon Riggs
2ndQuadrant http://www.2ndQuadrant.com
---(end of broadcast)---
TIP 6: ex
