Tom Lane writes:
I think that a more general solution would be the ability to select a
locale (and hence a sort order) per-column, as the SQL spec envisions.
It is a general solution, but not for this problem. The problem was to
make all locales equally suitable for certain optimizations, not
Tom Lane writes:
(the documentation build at developer.postgresql.org doesn't seem to
have updated since before the server move :-()
The program called onsgmls (or maybe nsgmls) is missing. Marc, can
you please install it? It should be in a package called opensp.
--
Peter Eisentraut
We have been there, done that, and decided it was a bad idea. I suggest
you do a little reading in the mail list archives.
I have searched the lists archives for the words commit, autocommit and
transaction but couldn't find any discussion on wheter to give a database
administrator the option
[ moving this thread to a more appropriate place ]
Sean Chittenden [EMAIL PROTECTED] writes:
It would also be interesting to combine this with Rod's idea of
driving describe-type queries by table instead of hardwired code.
Imagine that the backend's show foo command first looks for foo
as a
Bruce Momjian writes:
Our default indexes will be able to do =, , , ORDER BY, and the
special index will be able to do LIKE, ORDER BY, and maybe equals. Do I
have that correct?
The default operator class supports comparisons (=, , , etc.) and ORDER
BY based on those operators. The other
Sean Chittenden writes:
Keep krb4 in the tree for 7.4, but before 7.4 gets released, the
documentation and release notes need to state that krb4 has been
depreciated and that it will be removed before 7.5. I'll add submit a
patch for the updated verbiage in a bit. -sc
I object to treating
Hi all,
I just get postgresql from cvs and could compile perfectly on cygwin!!
Great work guys!!!
But when I run the initdb script, it fails with the following message:
The database cluster will be initialized with locale C.
Fixing permissions on existing directory /var/pgsqlcvs/... ok
creating
Tom Lane writes:
Are there any locales that claim that not-physically-identical strings
are equal?
In Unicode there are plenty such combinations.
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of broadcast)---
TIP 5: Have you checked our
On Fri, 2003-05-30 at 17:06, Oleg Bartunov wrote:
Hello,
Is there interest to storing and indexed access methods for xml in
postgresql ? While I don't use xml in my applications but I see
Yes. But my GiST skills were never up to it!
possible directions to develop contrib module with
One thing that is doable with psql's current hard-wired approach, but
doesn't seem easy to do with this solution, is automatic localization
of strings such as column headings. Rod had looked at that a little
in his trial patch to convert psql's \d stuff to table-driven form,
but AFAIR he
Hi Guys,
I really need a solution to this one :(
What is the encoding of the database names in the pg_database table? As far
as I can tell, each row is saved in the encoding of the database from which
it is created? In my application, the actual names change from gobbledygook
to proper
Peter Eisentraut wrote:
Bruce Momjian writes:
Our default indexes will be able to do =, , , ORDER BY, and the
special index will be able to do LIKE, ORDER BY, and maybe equals. Do I
have that correct?
The default operator class supports comparisons (=, , , etc.) and ORDER
BY based on
Peter Eisentraut wrote:
Sean Chittenden writes:
Keep krb4 in the tree for 7.4, but before 7.4 gets released, the
documentation and release notes need to state that krb4 has been
depreciated and that it will be removed before 7.5. I'll add submit a
patch for the updated verbiage in a
I am trying to figure out whether there is a TODO item in this thread.
The basis of the discussion appeared to be whether we are honoring the
spec by executing before/after statement/row/constraint triggers
properly, and if we are not, is it desirable/significant if we break the
spec.
Which
Christopher Kings-Lynne [EMAIL PROTECTED] writes:
What is the encoding of the database names in the pg_database table? As far
as I can tell, each row is saved in the encoding of the database from which
it is created?
That sounds about right. If you're using databases of different
encodings
FAQ_DEV updated. Thanks.
---
Andrew Dunstan wrote:
The Developer FAQ is slightly awry for emacs settings, or at least it was for my
setup.
Here's what I ended up getting to work
;;-
(c-add-style
That sounds about right. If you're using databases of different
encodings in the same installation, it would probably be wise to
restrict yourself to the intersection of those encodings when choosing
database names.
Bummer. So there's no one encoding I can set it to :( Actually, since the
Christopher Kings-Lynne [EMAIL PROTECTED] writes:
How do I get the encoding of the server?
There is none. The per-database encodings are the only truth.
We aren't likely to institute one in future, either; the trend
seems to be more towards decentralization than the reverse.
I would suggest
On 1 Jun 2003 at 11:10, Manfred Spraul wrote:
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
19 matches
Mail list logo
