Hi,
I a little work with encodings (Japanese, Latin(s)) and I see that
PG use non-standard encoding names.
Why is here SJIS instead Shift-JIS, EUC_JP intead EUC-JP,
Latin2 instead ISO-8859-2 ?
It is not good for example for applications that output data to HTML and
needs set correct
I think a formating mode where only the relevant digits are written
to the output would be great as an alternative to the discussed
fixed formatting strings. In this context i think of 'relevant'
as in the following:
'Output as few characters as possible but ensure that scanf is
still able to
I a little work with encodings (Japanese, Latin(s)) and I see that
PG use non-standard encoding names.
Why is here SJIS instead Shift-JIS, EUC_JP intead EUC-JP,
Latin2 instead ISO-8859-2 ?
It is not good for example for applications that output data to HTML and
needs set correct
But HTML meta tags used to use their own encoding names such as
x-euc-jp, x-sjis
Not sure, my mozilla understand "ISO--x", "Shift-JIS" format too.
But it's irrelevant, important is that something like "Latin2" or "SJIS"
or "EUC_JP" are less standard names. And here aren't HTML only,
At 10:19 21/02/01 +0100, Robert Schrem wrote:
The advantage would be, that we only generate as much ASCII data
as absolutly neccessary to rebuild the original data exactly.
At least this is what I would expect from pg_dump.
pg_dump is only one side of thre problem, but the simplest solution
But HTML meta tags used to use their own encoding names such as
x-euc-jp, x-sjis
Not sure, my mozilla understand "ISO--x", "Shift-JIS" format too.
But it's irrelevant, important is that something like "Latin2" or "SJIS"
or "EUC_JP" are less standard names. And here aren't HTML
On Wed, 21 Feb 2001, you wrote:
At 10:19 21/02/01 +0100, Robert Schrem wrote:
The advantage would be, that we only generate as much ASCII data
as absolutly neccessary to rebuild the original data exactly.
At least this is what I would expect from pg_dump.
pg_dump is only one side of thre
You not must change current names, you can add to pg_conv_tbl[] new lines
with names synonym for already existing encoding...
{LATIN1, "LATIN1", 0, latin12mic, mic2latin1, 0, 0},
{LATIN1, "ISO-8859-1", 0, latin12mic, mic2latin1, 0, 0},
And if you order this table by alphabet and in
On Wed, 21 Feb 2001, Thomas Lockhart wrote:
You not must change current names, you can add to pg_conv_tbl[] new lines
with names synonym for already existing encoding...
{LATIN1, "LATIN1", 0, latin12mic, mic2latin1, 0, 0},
{LATIN1, "ISO-8859-1", 0, latin12mic, mic2latin1, 0, 0},
Philip Warner writes:
At 22:29 20/02/01 +0100, Peter Eisentraut wrote:
Tom Lane writes:
And we frequently see questions from users about how they can display
fewer digits than the system wants to give them --- or, more
generally, format the output in some special form.
to_char()
Peter Eisentraut wrote:
Hannu Krosing writes:
It would be nice if someone (pgsql inc., great bridge, etc.) provided a
central web page for registering the results so that you won't need to
scan athe whole list to find out if your platform is already tested.
"Platform already tested" is
Is there any way in psql to connect to a database and reduce the run
priority of the child thread it kicks off ?
i.e. equivalent of 'nice' on the thread?
From first looks at the code, it seems to fork off the process and there is
a pid that can be niced.
If an extra run level parameter is passed
As you probably know, there is already a binary search algorithm coded
up for the date/time string lookups in utils/adt/datetime.c. Since that
lookup caches the last value (which could be done here too) most lookups
are immediate.
Are you proposing to make a change Karel, or just
Hannu Krosing writes:
It would be nice if someone (pgsql inc., great bridge, etc.) provided a
central web page for registering the results so that you won't need to
scan athe whole list to find out if your platform is already tested.
"Platform already tested" is a misguided concept. Almost
On Thu, 22 Feb 2001, Tatsuo Ishii wrote:
As you probably know, there is already a binary search algorithm coded
up for the date/time string lookups in utils/adt/datetime.c. Since that
lookup caches the last value (which could be done here too) most lookups
are immediate.
Are
Tom Lane wrote:
platform) i686-pc-linux-gnu, compiled by GCC
egcs-2.91.60(turbolinux 4.2)
min delay) 10msec according to your test program.
-B) 64 (all other settings are default)
Thanks. Could I trouble you to run it again with a larger -B, say
1024 or 2048? What I've
Peter Eisentraut [EMAIL PROTECTED] writes:
Tatsuo Ishii writes:
o regex/utils.h included twice somewhere. I added #ifndef
UTILS_H... to utils.h
Okay.
Actually, the problem is probably gone. c.h was including regex/utils.h
if the platform didn't have memmove(), but I thought that was a very
On Wed, 21 Feb 2001, The Hermit Hacker wrote:
On Wed, 21 Feb 2001, Vince Vielhaber wrote:
On Wed, 21 Feb 2001, The Hermit Hacker wrote:
Vince, is this something that PostgreSQL.Org can have on the web page
relatively quickly?
The beta or registering the results? After the
I've looked through my archives of pgsql-general and pgsql-hackers and
haven't seen this, but I do tend to flush the deleted messages
occasionally. I'm trying to get a build off the current CVS tree, but
my working build is from Sunday evening, so I feel moderately current.
Two builds of
Dan Lyke [EMAIL PROTECTED] writes:
On my development machine (Built from CVS late Sunday, February 18), I
get:
test=# select count(id) from abc;
ERROR: ExecEvalAggref: no aggregates in this expression context
Try make distclean, configure, make all. Someone else reported this
same
o SunOS4 does not have atexit (used in psql). -- igore it
Maybe on_exit() is available, or even more portable?
Let me check it.
SunOS4 has on_exit. Can we change atexit to on_exit?
o to make shared library I have added an entry for SunOS4 in
Makefile.shlib.
I'm not sure
On Wed, 21 Feb 2001, The Hermit Hacker wrote:
On Wed, 21 Feb 2001, Vince Vielhaber wrote:
On Wed, 21 Feb 2001, The Hermit Hacker wrote:
Vince, is this something that PostgreSQL.Org can have on the web page
relatively quickly?
The beta or registering the results? After the
o no RAND_MAX or EXIT_FAILURE found. I simply added them to c.h.
EXIT_FAILURE is defined in src/bin/psql/settings.h; I can't find it used
outside psql.
So SunOS should be ok with this in current.
RAND_MAX should be inside an #ifndef RAND_MAX, not in a
SunOS specific section.
Ok.
o
Peter Eisentraut [EMAIL PROTECTED] writes:
I doubt that it ever really worked, or could work, to install a new
version over an old one without deleting the old one first. This here is
just one problem. We can't be making these funny workarounds every time
the set of installed user visible
I have a bunch of machines here, some are rather old (K6-200s,P133s, some
486s etc) but they're just collecting dust now. I would be more than happy
to install any OS and do build testing for PostgreSQL is there is a need..
What OSes need to have PostgreSQL built/tested on that the developers
Tom Lane writes:
Deleting files in the install directory during installation is very
inappropriate. At least let's try to get rid of it for 7.2.
I don't like it much either, but I agree with Larry that it's an
essential transition step for now. Perhaps we can remove it again
in 7.2 or
* Peter Eisentraut [EMAIL PROTECTED] [010221 16:09]:
Tom Lane writes:
Deleting files in the install directory during installation is very
inappropriate. At least let's try to get rid of it for 7.2.
I don't like it much either, but I agree with Larry that it's an
essential
* Lamar Owen [EMAIL PROTECTED] [010221 16:36]:
Vince Vielhaber wrote:
the things Lamar and Peter also mentioned. Note: I'm probably 450
messagees behind due to a 2 day dsl outage; I may have missed some of
the conversation. Some messages trickled in, the rest flooded in over
night. I
Peter Eisentraut [EMAIL PROTECTED] writes:
Larry Rosenman writes:
AND make sure we nuke any OLD version in $(destdir)/include... Which
will cause a file not found vs. compile errors based on redeclares...?
Deleting files in the install directory during installation is very
inappropriate.
Tatsuo Ishii writes:
o c.h 's sunos4 part should not include varargs.h. (Tom has already
fixed it) Instead, stdlib.h and stdarg.h should be included.
This should be okay by now.
o no RAND_MAX or EXIT_FAILURE found. I simply added them to c.h.
EXIT_FAILURE is defined in
Philip Warner [EMAIL PROTECTED] writes:
The other issues, like what is sent to psql via interfaces like odbc
(currently text) should be application/DBA based and setable on a
per-attribute basis. eg. some applications want 1. because the data
came from a piece of hardware with a know
Tatsuo Ishii [EMAIL PROTECTED] writes:
o SunOS4 does not have atexit (used in psql). -- igore it
Maybe on_exit() is available, or even more portable?
SunOS4 has on_exit. Can we change atexit to on_exit?
atexit is ANSI C. on_exit is not found here (HPUX) at all. Looks
like we
The Hermit Hacker [EMAIL PROTECTED] writes:
Vince, is this something that PostgreSQL.Org can have on the web page
relatively quickly?
On Wed, 21 Feb 2001, Hannu Krosing wrote:
It would be nice if someone (pgsql inc., great bridge, etc.) provided a
central web page for registering the
Tatsuo Ishii [EMAIL PROTECTED] writes:
o SunOS4 does not have atexit (used in psql). -- igore it
Maybe on_exit() is available, or even more portable?
SunOS4 has on_exit. Can we change atexit to on_exit?
atexit is ANSI C. on_exit is not found here (HPUX) at all. Looks
like we need another
Hi Vince,
That's really nifty.
I don't know how to word it, but I think it might be worth including
something to find out if the machine was "out-of-the box" with just the
recommended installation utils (i.e. a "new build" of AIX, NT, Solaris,
etc, then gcc, bison or whatever) vs. a machine
On Wed, 21 Feb 2001, Vince Vielhaber wrote:
On Wed, 21 Feb 2001, The Hermit Hacker wrote:
Vince, is this something that PostgreSQL.Org can have on the web page
relatively quickly?
The beta or registering the results? After the last time I won't
put beta releases on the website, but
Larry Rosenman writes:
AND make sure we nuke any OLD version in $(destdir)/include... Which
will cause a file not found vs. compile errors based on redeclares...?
Deleting files in the install directory during installation is very
inappropriate. At least let's try to get rid of it for 7.2.
What about adding a field where they paste the output of 'uname -a' on their
system...?
Chris
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Justin Clift
Sent: Thursday, February 22, 2001 12:52 PM
To: Vince Vielhaber
Cc: [EMAIL PROTECTED]
I wrote:
Chris Storah [EMAIL PROTECTED] writes:
What I am looking for is a postgres system that runs 100 users or so at
'full speed', and major day long queries at a 'when idle' priority.
The trouble here is that CPU nice doesn't (on most platforms) change the
behavior of the I/O scheduler,
Chris Storah [EMAIL PROTECTED] writes:
Is there any way in psql to connect to a database and reduce the run
priority of the child thread it kicks off ?
i.e. equivalent of 'nice' on the thread?
Not at the moment, though it'd be a fairly trivial hack on postgres.c
to add a "-nice n" backend
but the changes in the include structure force us to.
If someone includes the old ones that aren't supposed to be there, we cause
non-obvious compile errors.
LER
-Original Message-
From: Peter Eisentraut [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 21, 2001 10:56 AM
To: Larry
Oops.
I rechecked the start up script, and the 7.0.3 doesn't have fsync off or
whatever. Dunno why I thought it was on (heh maybe because it was a lot
faster than 6.5.3!).
Hmm, this means 7.0.3 is quite fast...
Cheerio,
Link.
Just another data point.
I downloaded a snapshot yesterday - Changelogs dated Feb 20 17:02
It's significantly slower than "7.0.3 with fsync off" for one of my webapps.
7.0.3 with fsync off gets me about 55 hits per sec max (however it's
interesting that the speed keeps dropping with continued
43 matches
Mail list logo
