Am Montag, 1. November 2004 07:41 schrieb Dennis Bjorklund:
For each type we need to have convertion functions to and from strings.
Any suggestion of how to represent these as strings now when it's a string
plus two oid's? This is a though one..
A collation implies a character set, so you only
Am Montag, 1. November 2004 22:16 schrieb Roland Volkmann:
now, where the native Win32-Version of PostgreSQL is nearly ready for
Production use, I'm still missing support of WIN1252 charset. And UTF-8
can't be used on server side in West Europe, because it's implementation
isn't complete yet
Gaetano,
I do not consider my design as unsafe, this is for example how a
cache works: expose a read without side effect but updating internal
statistics. After all the read will not alter the data that it expose
but other data that the user even don't know the existence.
However I think that that
It makes no difference on any of my systems, so at least it doesn't
completely solve the problem. I haven't heard any
confirmation on wether
it partially solves it.
It certainly does not solve any part of your problem. I think your problem
is a permissions problem.
It does however make
o fix shared memory on Win2k terminal server
We might be able to just mark this as not supported.
The shmem code works in a terminal server session with or without the patch.
Magnus had a different problem, probably permissions. Since I do not have a
non admin user (on a TS server)
It is my opinion that we should allow pg to run as Admin on Windows, at least
with an override option. Services that run under a specified user are a headache
on Win32, because you need to store a password, and a lot of systems only have
one user.
Well I don't know that I agree with this.
Neil Conway [EMAIL PROTECTED] writes:
One alternative is to create memory contexts for each insertion /
creation / deletion operation, but that is pretty ugly, and probably
inefficient for insertion/deletion.
I don't believe memory context creation is very much worse than a malloc
(and it's
Tom Lane wrote:
I don't believe memory context creation is very much worse than a malloc
(and it's certainly not that much worse than a context reset).
If you can't buy back the time spent by avoiding some retail pfrees, then
this whole exercise becomes very questionable anyway.
Hmm, okay -- I'll
On Tue, 2 Nov 2004, Peter Eisentraut wrote:
A collation implies a character set, so you only need to store one piece of
information anyway.
No, a collation implies a character repertoire like UCS (unicode), it can
apply to several character sets like UTF8 and UTF16.
One can enumerate all
o fix shared memory on Win2k terminal server
We might be able to just mark this as not supported.
The shmem code works in a terminal server session with or
without the patch.
Magnus had a different problem, probably permissions. Since I
do not have a non admin
Am Montag, 1. November 2004 07:41 schrieb Dennis Bjorklund:
For each type we need to have convertion functions to and from strings.
Any suggestion of how to represent these as strings now when it's a string
plus two oid's? This is a though one..
A collation implies a character set, so
Just one question about the actual implementation of the patch - why are
you setting the OS version *before* you call GetVersionEx()?
The Microsoft Example did a memset on the structure before calling void GetVersionEx().
Setting it to a version that needs the Global\ is only a safeguard
Just one question about the actual implementation of the
patch - why
are you setting the OS version *before* you call GetVersionEx()?
The Microsoft Example did a memset on the structure before
calling void GetVersionEx().
The docs only say you have tos et the dwOSVersionInfoSize
Greg Stark wrote:
Tom Lane [EMAIL PROTECTED] writes:
On the whole I'm unconvinced that this is worth the trouble. One of the
reasons for allowing people to move databases around is to determine
where their temp files go.
The one scenario I would expect to see is having the temp
Am Dienstag, 2. November 2004 13:15 schrieb Dennis Bjorklund:
On Tue, 2 Nov 2004, Peter Eisentraut wrote:
A collation implies a character set, so you only need to store one piece
of information anyway.
No, a collation implies a character repertoire like UCS (unicode), it can
apply to
Am Dienstag, 2. November 2004 13:53 schrieb Tatsuo Ishii:
In my understanding the relation between charset and collation is
1:N. Thus storing only a collation is sufficient to determine the
charset. However a charset cannot determine a collation.
Exactly.
--
Peter Eisentraut
On Tue, 2 Nov 2004, Peter Eisentraut wrote:
For the theoretical specification of a collation, it might suffice to
know the character repertoire. But I think in practice, the
implementation of a collation will require knowing the specific
character encoding.
The named entity that is called a
Hi all,
I need a help and an advice on playing around execution plans. I need a direct
access to a 'plan structure' and change some fields. Even one step more, I
need to create an execution plan directly w/o issuing an SQL statement (i.e.
skipping parser and optimizer phases) and initialize
Gaetano,
I do not consider my design as unsafe, this is for example how a
cache works: expose a read without side effect but updating internal
statistics. After all the read will not alter the data that it expose
but other data that the user even don't know the existence.
At issue is the
Josh Berkus wrote:
Gaetano,
I do not consider my design as unsafe, this is for example how a
cache works: expose a read without side effect but updating internal
statistics. After all the read will not alter the data that it expose
but other data that the user even don't know the existence.
At
Dennis Bjorklund wrote:
The named entity that is called a collation works for a character
repertoire. It would need to handle different charsets for that
repertoire of course. So there would be one collation called say
ucs_sv and not utf8_sv, utf16_sv, utf32_sv.
Again, theoretically, this
I may have asked this before, but I don't think I got a response.
Is there any reason for make installcheck to run the serial schedule
when make check runs the parallel one? If there is, could we perhaps
invent make installcheck-par to run the parallel tests on an installed
database?
//Magnus
I can confirm this bug.
---
Wood, Bruce wrote:
I'm not sure if this goes here or to bugs, but it seems obvious
(to me) that if this problem existed elsewhere, it would have
been brought up by now.
In the first version
On Tue, 2004-11-02 at 01:44, Tom Lane wrote:
Neil Conway [EMAIL PROTECTED] writes:
I think there needs to be a way to list all the objects in a schema.
This doesn't seem especially helpful to me, because you'd have to fit a
bunch of different object types into a one-size-fits-all output,
Dennis Bjorklund wrote:
The named entity that is called a collation works for a character
repertoire. It would need to handle different charsets for that
repertoire of course. So there would be one collation called say
ucs_sv and not utf8_sv, utf16_sv, utf32_sv.
Again, theoretically,
25 matches
Mail list logo
