Hi,
Here are patches against tsearch2 with CVS head. Currently tsearch2
does not work with multibyte encoding which uses C locale. These
patches are intended to solve the problem by using PostgreSQL in-house
multibyte function instead of mbstowcs which does not work with C
locale. Also iswalpha
Gurjeet Singh [EMAIL PROTECTED] writes:
I thought that if the author of the code (which, now I see, is you)
No, it was Jan IIRC.
And surely we are never going
to make VACUUM force a complete REINDEX as the comment suggests.
In that case, can the comment be changed!
Even though it's a poor
TL == Tom Lane [EMAIL PROTECTED] writes:
TL Personally I don't find the argument about someday we might want
TL to support measurements in millibits to be convincing at all, and
TL certainly it seems weaker than the argument that units should be
TL case insensitive because everything else in
Benny Amorsen [EMAIL PROTECTED] writes:
TL == Tom Lane [EMAIL PROTECTED] writes:
TL Personally I don't find the argument about someday we might want
TL to support measurements in millibits to be convincing at all, and
TL certainly it seems weaker than the argument that units should be
TL case
I'm wondering if Gevik has had any time for further work on
http://archives.postgresql.org/pgsql-hackers/2006-09/msg01738.php ?
FWIW, I'm running into this trying to create a 'raw' domain that would
automagically convert hex strings into actual binary data for storage in
a bytea. My intention was
The SQL2003 spec adds optional NULLS FIRST and NULLS LAST modifiers
for ORDER BY clauses. Teodor proposed an implementation here:
http://archives.postgresql.org/pgsql-patches/2006-12/msg00019.php
which I didn't care for at all:
http://archives.postgresql.org/pgsql-hackers/2006-12/msg00133.php
[EMAIL PROTECTED] (Joshua D. Drake) writes:
The reason I wanted to use PGP is that I already have a PGP key. X.509
certificates are far too complicated (a certificate authority is a
useless extra step in my case).
Complete side note but one feature that I brought up to my team a
potentially
Jim C. Nasby [EMAIL PROTECTED] writes:
FWIW, I'm running into this trying to create a 'raw' domain that would
automagically convert hex strings into actual binary data for storage in
a bytea.
I think you've got 0 chance of implementing that as a domain rather than
an independent type. Without
I will start processing the patches held for 8.3 this week or next, now
that the holiday break is over:
http://momjian.postgresql.org/cgi-bin/pgpatches_hold
--
Bruce Momjian [EMAIL PROTECTED]
EnterpriseDBhttp://www.enterprisedb.com
+ If your life is a hard drive, Christ can
Bruce Momjian wrote:
I will start processing the patches held for 8.3 this week or next, now
that the holiday break is over:
http://momjian.postgresql.org/cgi-bin/pgpatches_hold
Some of these look obsolete. Also,
. the plperl out params patch needs substantial rework by its author,
Tom Lane wrote:
Jim C. Nasby [EMAIL PROTECTED] writes:
FWIW, I'm running into this trying to create a 'raw' domain that would
automagically convert hex strings into actual binary data for storage in
a bytea.
I think you've got 0 chance of implementing that as a domain rather than
an
I came across this when looking through the patches_hold queue link that
Bruce sent out.
http://momjian.us/mhonarc/patches_hold/msg00162.html
There is no patch or anything associated with it, just the suggestion that
it be put in when 8.3 devel starts up.
Just thought I'd put this back out
Andrew Dunstan wrote:
Bruce Momjian wrote:
I will start processing the patches held for 8.3 this week or next, now
that the holiday break is over:
http://momjian.postgresql.org/cgi-bin/pgpatches_hold
Some of these look obsolete. Also,
. the plperl out params patch needs
D'Arcy J.M. Cain darcy@druid.net writes:
I changed this and a few other things. I didn't see any response to my
question though. Shall I go ahead and commit now so that we can test
in a wider setting? I haven't committed anything in years and I am
hesitant to do so now without consencus.
14 matches
Mail list logo
