Tonight regular CVS is very slow to generate a diff. Does anyone know
why? Load average is only 2.0.
--
Bruce Momjian| http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Chris
[EMAIL PROTECTED] writes:
> While writting some code for the backend (some SPI-like functions for a
> project) I saw this message:
> "WARNING: problem in alloc set ExecutorState: bogus aset link in block
> 0x8301270, chunk 0x8304458"
> I think there is something wrong with some of the memory
On Sun, 2 Jan 2005, Roland Volkmann wrote:
2. I visited some of the mirrors as well as ftp.postgresql.org and there
the source tarballs of rc3 have file date 31.12.2004 22:39 while Tom
Lane posted last corrections related to copyright messages on 01.01.2005
23:14, and Bruce Momjian posted Update
> >I do understand the problem, but don't undertstand the decision you
> >guys made. The fact that UPPER/LOWER and some other functions does not
> >work in win32 is surely a problem for some languages, but not a
> >problem for otheres. For example, Japanese (and probably Chinese and
> >Korean) does
> "Magnus Hagander" <[EMAIL PROTECTED]> writes:
> > I didn't consider the C locale. Do you know for a fact that it works
> > there on win32 as well, or is that an assumption?
>
> It should work. The only use of strcoll() in the backend is in
> varstr_cmp which uses strncmp() instead for C locale.
Hello All,
I'm new in postgres development, but I really
interested in the development of label security for postgres. Label
security provides mandatory acces control to the records in a table, like Oracle
Label Security, and basically this is my intention to do. Well, I want to
know if
Hi everybody!
While writting some code for the backend (some SPI-like functions for a
project) I saw this message:
"WARNING: problem in alloc set ExecutorState: bogus aset link in block
0x8301270, chunk 0x8304458"
I think there is something wrong with some of the memory allocations I do,
Added to TODO:
* Allow building with directories containing spaces
---
Andrew Dunstan wrote:
>
>
> Tom Lane wrote:
>
> >Pursuant to Theodore Petrosky's recent trouble report, I thought I would
> >see what happens
> Actually, the standard Windows place to put software is Program Files,
Actually,. it's not... it's %ProgramFiles% or
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\ProgramFilesDir since the
name of "C:\Program Files" may vary depending on the language of the OS.
> and programs that don't do th
>>Along similar lines, when I installed RC1 on a windows box it
>installed it
>>under the "program files" directory. Now, this was fine for
>most cases, but
>>when I had to use some of the command line tools it was
>really crappy trying
>>to write explicit directories under dos. I generally c
Robert Treat wrote:
Along similar lines, when I installed RC1 on a windows box it installed it
under the "program files" directory. Now, this was fine for most cases, but
when I had to use some of the command line tools it was really crappy trying
to write explicit directories under dos. I gene
"Magnus Hagander" <[EMAIL PROTECTED]> writes:
> I didn't consider the C locale. Do you know for a fact that it works
> there on win32 as well, or is that an assumption?
It should work. The only use of strcoll() in the backend is in
varstr_cmp which uses strncmp() instead for C locale. Lack of
wo
>I do understand the problem, but don't undertstand the decision you
>guys made. The fact that UPPER/LOWER and some other functions does not
>work in win32 is surely a problem for some languages, but not a
>problem for otheres. For example, Japanese (and probably Chinese and
>Korean) does not have
I do understand the problem, but don't undertstand the decision you
guys made. The fact that UPPER/LOWER and some other functions does not
work in win32 is surely a problem for some languages, but not a
problem for otheres. For example, Japanese (and probably Chinese and
Korean) does not have a con
On Friday 31 December 2004 20:03, Andrew Dunstan wrote:
> Tom Lane wrote:
> >Pursuant to Theodore Petrosky's recent trouble report, I thought I would
> >see what happens if you try to build Postgres in a directory whose path
> >contains spaces, or if the install prefix contains spaces.
> >
> >It do
15 matches
Mail list logo