Re: [HACKERS] Additional supplied modules

2011-10-13 Thread Tom Lane
Josh Berkus writes: > On 10/13/11 6:32 AM, Thom Brown wrote: >> Could we somehow categorise these, and also do something to clarify >> that SPI is a collection of extensions rather than an extension >> itself? > Alternately we should clean up SPI and break it out into its separate > extensions.

Re: [HACKERS] Additional supplied modules

2011-10-13 Thread Thom Brown
On 13 October 2011 19:46, Dimitri Fontaine wrote: > Josh Berkus writes: >> On 10/13/11 6:32 AM, Thom Brown wrote: >>> Could we somehow categorise these, and also do something to clarify >>> that SPI is a collection of extensions rather than an extension >>> itself? >> >> Alternately we should cle

Re: [HACKERS] Additional supplied modules

2011-10-13 Thread Dimitri Fontaine
Josh Berkus writes: > On 10/13/11 6:32 AM, Thom Brown wrote: >> Could we somehow categorise these, and also do something to clarify >> that SPI is a collection of extensions rather than an extension >> itself? > > Alternately we should clean up SPI and break it out into its separate > extensions.

Re: [HACKERS] Additional supplied modules

2011-10-13 Thread Josh Berkus
On 10/13/11 6:32 AM, Thom Brown wrote: > Could we somehow categorise these, and also do something to clarify > that SPI is a collection of extensions rather than an extension > itself? Alternately we should clean up SPI and break it out into its separate extensions. -- Josh Berkus PostgreSQL Exp

[HACKERS] Additional supplied modules

2011-10-13 Thread Thom Brown
I've been thinking about the terminology used for various tools and extensions in PostgreSQL. The documentation bundles all them together in "Additional Supplied Modules, but really some are tools, some are libraries and some are extensions: Tools: oid2name pg_archivecleanup pgbench pg_standby pg