Обсуждение: Where is hstore?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, sorry if I'm on the wrong list (tell me so!). I'd like to know whether hstore isn't supposed to be in contrib any more and where it is supposed to live nowadays (I was close to file a complaint to my distributor until I discovered that it isn't in the 8.1 upstream source). Thanks - -- tomás -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFE6yt+Bcgs9XrR2kYRAvmBAJoC2GqNhPe0iiiYF5pwpfR+OUcaBQCfQoJy zvP+RZ2sWH5qhMjPV1ZBkm8= =bbs+ -----END PGP SIGNATURE-----
tomas@tuxteam.de wrote: > Hi, > > sorry if I'm on the wrong list (tell me so!). I'd like to know whether > hstore isn't supposed to be in contrib any more and where it is supposed > to live nowadays (I was close to file a complaint to my distributor > until I discovered that it isn't in the 8.1 upstream source). > > When has it ever been? cheers andrew
tomas@tuxteam.de wrote: > Hi, > > sorry if I'm on the wrong list (tell me so!). I'd like to know whether > hstore isn't supposed to be in contrib any more and where it is supposed > to live nowadays (I was close to file a complaint to my distributor > until I discovered that it isn't in the 8.1 upstream source). hstore can be found here: http://www.sai.msu.su/~megera/postgres/gist/ but it has never actually been part of contrib so I'm not sure what you are complaining about ? Stefan
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, Aug 22, 2006 at 04:06:22PM +0000, tomas@tuxteam.de wrote: > Hi, > > sorry if I'm on the wrong list (tell me so!). I'd like to know whether > hstore [...] I've been set right. Seems hstore was never in contrib. Sorry for the noise. BTW: any reason it isn't? It is very cool... Regards - -- tomás -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFE6zMSBcgs9XrR2kYRAobhAJ4j1PLayyJneVUSrdlzfPrnKVRfFACfdjP0 nlKNdOOW076ZdsNDFKK1fgA= =BI5g -----END PGP SIGNATURE-----
tomas@tuxteam.de writes:
> I've been set right. Seems hstore was never in contrib. Sorry for the
> noise.
> BTW: any reason it isn't? It is very cool...
AFAIR the authors have never proposed it for inclusion.
regards, tom lane
On Aug 22, 2006, at 17:01 , Tom Lane wrote: > tomas@tuxteam.de writes: >> I've been set right. Seems hstore was never in contrib. Sorry for the >> noise. > >> BTW: any reason it isn't? It is very cool... > > AFAIR the authors have never proposed it for inclusion. According to http://www.sai.msu.su/~megera/postgres/gist/hstore/ README.hstore : "Stable version, included into PostgreSQL distribution, ... version 2 (June 1991)." -M
AgentM <agentm@themactionfaction.com> writes: > On Aug 22, 2006, at 17:01 , Tom Lane wrote: >> AFAIR the authors have never proposed it for inclusion. > According to http://www.sai.msu.su/~megera/postgres/gist/hstore/ > README.hstore : > "Stable version, included into PostgreSQL distribution, ... version 2 > (June 1991)." 1991? There's a typo there somewhere. But anyway it has never actually been in the distribution, and the closest thing to a proposal I can find in the archives is http://archives.postgresql.org/pgsql-hackers/2003-05/msg00763.php which specifically says "not released yet". regards, tom lane
> AFAIR the authors have never proposed it for inclusion. We'll be glad if hstore will be in main tarball. As I remember, when we suggest (may be, in private exchange of letters) to include it, somebody says that hstore breaks "relational" in db. Lastest version is located at http://www.sigaev.ru/cvsweb/cvsweb.cgi/hstore/ Note, in this year there are a several questions about inclusion in mail lists: http://archives.postgresql.org/pgsql-hackers/2006-05/msg00079.php http://archives.postgresql.org/pgsql-hackers/2006-07/msg00727.php http://archives.postgresql.org/pgsql-hackers/2006-08/msg01412.php And several questions in private mail... Now hstore is stable module. -- Teodor Sigaev E-mail: teodor@sigaev.ru WWW: http://www.sigaev.ru/
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, Aug 23, 2006 at 01:39:34PM +0400, Teodor Sigaev wrote: > >AFAIR the authors have never proposed it for inclusion. > > We'll be glad if hstore will be in main tarball. FWIW, I'd be glad too. > As I remember, when we > suggest (may be, in private exchange of letters) to include it, somebody > says that hstore breaks "relational" in db. This might be true, and I'm definitely not the one to judge that, but then... geometrical data types do the same, right? But it is way cool... imho the coolest application of gist (this combination of bitmap hash and gist). > Lastest version is located at http://www.sigaev.ru/cvsweb/cvsweb.cgi/hstore/ > > Note, in this year there are a several questions about inclusion in mail > lists: > http://archives.postgresql.org/pgsql-hackers/2006-05/msg00079.php > http://archives.postgresql.org/pgsql-hackers/2006-07/msg00727.php > http://archives.postgresql.org/pgsql-hackers/2006-08/msg01412.php > And several questions in private mail... > > Now hstore is stable module. I'm planning to try my hands on using it as an rdf triple store. Thanks for your good work - -- tomas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFE7D/bBcgs9XrR2kYRAic0AJ4hmwrvnX6zNirPqJL7ygD2wLkAIgCeLsA2 xXlELrI45f12/TQG3Xrn2sA= =fiG6 -----END PGP SIGNATURE-----
Teodor Sigaev <teodor@sigaev.ru> writes:
>> AFAIR the authors have never proposed it for inclusion.
> We'll be glad if hstore will be in main tarball. As I remember, when we suggest
> (may be, in private exchange of letters) to include it, somebody says that
> hstore breaks "relational" in db.
It seems there is no objection to adding hstore to contrib/. Please
commit it this week if you can.
regards, tom lane
I'm seeing the following compiler warnings from hstore on x86_64:
hstore_io.c: In function 'get_val':
hstore_io.c:51: warning: format '%d' expects type 'int', but argument 4 has type 'long int'
hstore_io.c: In function 'parse_hstore':
hstore_io.c:150: warning: format '%d' expects type 'int', but argument 4 has type 'long int'
hstore_io.c:158: warning: format '%d' expects type 'int', but argument 4 has type 'long int'
hstore_io.c:181: warning: format '%d' expects type 'int', but argument 4 has type 'long int'
It passes its regression test anyway, but these need to be fixed.
regards, tom lane