Peter Eisentraut [EMAIL PROTECTED] writes:
I don't understand why you call this a hack. Pattern matching and string
comparison simply work differently, so the proper solution is to use
different operator classes. After all, that's what operator classes exist
for. What is left to be desired?
A German computer magazine (c't 7/2003) tested the Intel C/C++ compiler
suite on Linux. Among the open-source projects they tried, PostgreSQL and
KDE were the only ones they couldn't get to compile at all.
I tried it out and made two simple changes (see below) to be able to
compile it. If no
Rasmus Resen Amossen [EMAIL PROTECTED] writes:
Therefor: Are there any plans to give the administrator an OPTION to turn
the behavior off through a parameter autocommit = boolean in the config
file?
We have been there, done that, and decided it was a bad idea. I suggest
you do a little
Mike Mascari [EMAIL PROTECTED] writes:
... is it possible the GEQO threshold, as a default, is too low?
It's been on the TODO list for awhile to investigate whether the current
default is still appropriate. A lot of planner details have changed
since we last twiddled it, and you're not the
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Has the single-byte LIKE penalty been eliminated, so we don't need to
consider using C as the default locale for initdb, right?
I'm still of the opinion that we should make C the default locale.
But I'm not sure where the consensus
I ran across a regression in unmodified cvs tip. On a 7.3.2 installation
I can do:
create table tse(f1 int, f2 int[], f3 text[]);
insert into tse values(1,'{69,42,54}', '{g,d,e}');
# select * from tse where 1 in (select f1);
f1 | f2 | f3
++-
1 | {69,42,54} |
Bruce Momjian [EMAIL PROTECTED] writes:
So, my understanding is that you would create something such as:
CREATE INDEX iix ON tab (LIKE col)
and that does LIKE lookups and knows how to do col LIKE 'abc%', but it
can't be used for = or ORDER BY, but it can be used for equality tests?
Hm.
Joe Conway [EMAIL PROTECTED] writes:
I ran across a regression in unmodified cvs tip.
Looks like I forgot to make markTargetListOrigin handle outer-scope
Vars (those with varlevelsup 0) :-(. Will fix, thanks for report!
regards, tom lane
...which is nice:
http://www.theregister.co.uk/content/31/30959.html
Regards, Dave
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
So, my understanding is that you would create something such as:
CREATE INDEX iix ON tab (LIKE col)
and that does LIKE lookups and knows how to do col LIKE 'abc%', but it
can't be used for = or ORDER BY, but it can be used for
Sean Chittenden wrote:
auth.c: In function `pg_krb5_recvauth':
auth.c:294: structure has no member named `user'
Ooops, my fault --- I didn't build with Kerberos support after
changing those field names.
Now that I think about it, there might be similar omissions in the
PAM or
Your patch has been added to the PostgreSQL unapplied patches list at:
http://momjian.postgresql.org/cgi-bin/pgpatches
I will try to apply it within the next 48 hours.
---
Teodor Sigaev wrote:
Patch for
Tom Lane wrote:
Peter Eisentraut [EMAIL PROTECTED] writes:
I'm a little uneasy with puttting too much extra burden on the GUC
mechanism, which is after all a system to configure the server, not to
retrieve or communicate data. Even the server_version thing recently
added doesn't make me
Added to TODO:
* Add config variable to prevent auto-adding missing FROM-clause
tables
---
Philip Warner wrote:
At 02:36 PM 29/04/2003 -0700, Josh Berkus wrote:
I'd far rather have a fatal query error
auth.c: In function `pg_krb5_recvauth':
auth.c:294: structure has no member named `user'
Ooops, my fault --- I didn't build with Kerberos support after
changing those field names.
Now that I think about it, there might be similar omissions in the
PAM or Kerberos4
And patch now in queue. :-)
---
Bruce Momjian wrote:
Added to TODO:
* Add config variable to prevent auto-adding missing FROM-clause
tables
Shridhar Daithankar wrote:
2) Native freeBSD threads
pthread.h in /usr/include and lc_r
Do you know if FreeBSD supports pthread_rwlock with
PTHREAD_PROCESS_SHARED? I'm trying to replace the LWLocks with
pthread_rwlocks.
What about other Unices?
--
Manfred
---(end
17 matches
Mail list logo
