On Jul 13, 2004, at 17:02, Bruce Momjian wrote:
One failing that has appeared during the 7.5 development cycle is that
we as a community haven't been able to provide timely feedback to
developers working on large feature additions.
I am particularly thinking of Alvaro (nested transactions) and
Frank Wiles wrote:
shared_buffers = 1 ( shared_buffers in pages )
shared_buffers = 100M ( 100 MBs of shared_buffers )
shared_buffers = 2048K ( 2MBs of shared_buffers )
I don't know if this is pedantic or just obsessive-compulsive,
but I think it should be MB and KB (or more
Marc G. Fournier wrote:
Not sure if I like the URLs, myself ... opinions?
You could try cvsspam, which is what I use in-house. Neil
posted the URL. It does HTML mail, so it'd probably belong
on a dedicated list. It's a huge help with the links,
though, see this sample:
Peter Eisentraut wrote:
How about this one: Everything we have moved from the core to gborg so
far has been a miserable failure. The code is no longer maintained, or
maintained by three different competing groups, the documentation has
disappeared, the portability is no longer taken care of, and
Tatsuo Ishii wrote:
initdb could even emit a warning if the --encoding option was
used without also specifying --no-locale.
Please don't do that. Most Asian chasets does not work with locale
enabled PostgreSQL installation. i.e. it returns WRONG SELECT
results. I've been telling this to Japanese
On 17. touko 2004, at 10:40, Tatsuo Ishii wrote:
Consider a program using JDBC on localhost. It can only reach to
PostgreSQL via TCP/IP.
Ah! Of course. That makes sense, and listening on 127.0.0.1 never
hurt anyone (except, of course, the tinfoil hat crowd nmapping
localhost in a frenzy...)
mk
Tatsuo Ishii wrote:
Is there any security risk if we enable tcpip_socket by default? We
restrict connection from localhost only by default so I think enabling
tcpip_socket adds no security risk. Please correct me if I am wrong.
Bruce Momjian wrote:
Right, and 7.5 will ship with tcp and localhost
Tom Lane wrote:
This code will only work if the database is running under an LC_CTYPE
setting that implies the same encoding specified by server_encoding.
However, I don't see that as a fatal objection, because in point of
fact
the existing upper/lower code assumes the same thing.
I think this
Marko Karppinen wrote:
I think this interaction between the locale and server_encoding is
confusing. Is there any use case for running an incompatible mix?
If not, would it not make sense to fetch initdb's default database
encoding with nl_langinfo(CODESET) instead of using SQL_ASCII?
Peter
On 3 March 2004, at 19:52, Bruce Momjian wrote:
The advantage of symlinks is that an administrator could see how things
are laid out from the command line.
One thing to keep in mind is that system administrators don't see
symlinks as being informational -- they see them as the actual UI
for the
On 11 Nov 2003, at 20:44, Peter Eisentraut wrote:
Do we have any data on how many people download the partial tarballs
(-base, -opt, etc.)? I have a feeling that more people are confused by
them than use them.
Even if they weren't useful for anything else, I think there's value in
the
On 8 Nov 2003, at 22:19, Tom Lane wrote:
After fixing the ps_status problems, I cannot observe any problem, with
or without system.c. However, I agree that it's a bad idea to
propagate
that hack forward when it's no longer needed. I've #ifdef'd out
system.c for OS X 10.3 and later. (I was
On Oct 24, 2003, at 18:37, Bruce Momjian wrote:
It is time for people to report their port testing. Please test
against
current CVS or beta5 and report your 'uname -a'.
This is with beta 5.
Darwin marko.karppinen.fi 7.0.0 Darwin Kernel Version 7.0.0: Wed Sep 24
15:48:39 PDT 2003;
Looking a bit further into this, it looks like random tests are
failing. Seems like an issue with the test harness on this
platform.
Does someone want a shell account to debug?
mk
On Oct 24, 2003, at 21:39, Marko Karppinen wrote:
6 out of 93 tests failed:
date ... FAILED
I'm just being an idiot, it's obviously a limits problem on the
platform.
It has a default max user processes limit of 100, which I was hitting.
I shut down a bunch of desktop apps, and it's now passing:
92 of 93 tests passed, 1 failed test(s) ignored.
(random was the one failing).
So I guess
On 14.10.2003, at 19:52, Tom Lane wrote:
This means that relaxing the check would require (a) finding out which
of the sub-flags break our code and which don't; (b) finding out how
the
answer to (a) has varied with gcc release; and (c) finding out how we
can test whether a given sub-flag is set
On 12.10.2003, at 03:52, James Wilson wrote:
I've done a checkout from CVS and performed a build under OS X Panther
7B85 with the non-hacked header files. The problem with the param.h
header file seems to be fixed, however the build is failing with
undefined symbols in libs:
I believe you have
James, we've spent some time lately with Mac OS X related changes to
the code base. Please try this again with a fresh CVS copy of
PostgreSQL and let us know if there are any further changes you think
we'd need to work properly with Panther.
Thanks,
mk
On 11.10.2003, at 04:32, James Wilson
flag only when linking them, but I think it'd lead
to much more maintenance and bloated Makefiles.
cheers
mk
Marko Karppinen [EMAIL PROTECTED] writes:
While we're on a Mac-related note, I managed to compile PostgreSQL on
Mac OS X 10.2 Jaguar with two-level namespace support.
http
Tom:
BTW, is anyone interested in looking into whether we can be made to
build without using either flag? I tried it and saw a number of
failures that looked like they traced to incompatible macro expansion.
This wouldn't surprise me if PG were some halfbaked package that only
got tested with
On lauantai, syys 20, 2003, at 23:37 Europe/Helsinki, Tom Lane wrote:
Is anyone on the list still running OS X 10.1, or anyway still using a
version of the OS X developer tools older than the Dec 2002 release?
It would be good to check if -no-cpp-precomp creates any problems on
any release that
21 matches
Mail list logo
