Le 12 juin 09 à 23:20, Tom Lane a écrit :
Dimitri Fontaine writes:
Le 12 juin 09 à 21:49, Tom Lane a écrit :
It seems to me it could still do
with a lot more detail to specify what API the functions are really
expected to implement.
What's bothering me is the fuzziness of the API
specificati
Dimitri Fontaine writes:
> Le 12 juin 09 à 21:49, Tom Lane a écrit :
>> It seems to me it could still do
>> with a lot more detail to specify what API the functions are really
>> expected to implement.
> I'm sorry I'm not following... I guess you're talking about a better
> high-level view of t
Hi,
Le 12 juin 09 à 21:49, Tom Lane a écrit :
Applied with some editorialization.
Thanks a lot :)
It seems to me it could still do
with a lot more detail to specify what API the functions are really
expected to implement.
I'm sorry I'm not following... I guess you're talking about a bette
Dimitri Fontaine writes:
> I've been working some more on this documentation:
Applied with some editorialization. It seems to me it could still do
with a lot more detail to specify what API the functions are really
expected to implement.
regards, tom lane
--
Sent via p
Hi,
I've been working some more on this documentation:
Le 20 mai 09 à 18:10, Dimitri Fontaine a écrit :
- consistent signature update for 8.4 (recheck arg)
- compress/decompress non void example
This means the multi-column support part is still missing, as proper
english review too.
But I
Hi,
Le 4 mai 09 à 14:24, Peter Eisentraut a écrit :
There aren't a lot of people who have the experience to write that
documentation. So if you want to improve it, you will have to write
it, or at
least organize the outline. Others can help cleaning it up.
For the record, here's the curre
On Wednesday 29 April 2009 16:43:44 Dimitri Fontaine wrote:
> The following documentation page explains the GiST API to extensions
> authors:
> I think we should be a little more verbose,
> I didn't propose a real doc patch mainly because english isn't my native
> language, and while you'll have
Hi,
The following documentation page explains the GiST API to extensions authors:
http://www.postgresql.org/docs/current/static/gist-implementation.htm
I think we should be a little more verbose, and at least explains some more
the big picture: same/consistent/union are responsible for correct
