?
In the SRA's code, the checkpoint thread opens each file (if it's not
already open of course) which has been written then fsync() it.
--
Tatsuo Ishii
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
OK, I've been spreading rumours about fixing the internationalization
problems, so let me make it a bit more clear. Here are the problems that
need to be fixed:
- Only one locale per process possible.
- Only one gettext-language per process possible.
- lc_collate and lc_ctype need to
. Another gottcha
with Unicode is the UTF-8 encoding (currently we use) consumes 3
bytes for each Kanji character, while other encodings consume only 2
bytes. IMO 3/2 storage ratio could not be neglected for database use.
--
Tatsuo Ishii
---(end of broadcast
Hi,
A problem related with view was reported from a user. I narrowed down
the problem and found it was related to some usage of views:
(note that with/without limit is not relevant)
test=# select count(a.*) from pg_indexes a limit 10;
server closed the connection unexpectedly
This
Tatsuo Ishii [EMAIL PROTECTED] writes:
test=# select count(a.*) from pg_indexes a limit 10;
server closed the connection unexpectedly
Hmmm ... the crash is certainly UnGood, but is there any reason we
should accept this query rather than generating an error? I don't
think it's legal
this?
--
Tatsuo Ishii
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
Are we going to regenerate the 7.4.1 tar ball?
--
Tatsuo Ishii
Peter Eisentraut - PostgreSQL wrote:
CVSROOT:/cvsroot
Module name:pgsql-server
Changes by: [EMAIL PROTECTED] 03/12/21 17:36:34
Modified files:
doc/src/sgml : Tag: REL7_4_STABLE release.sgml
I see following in the doc:
Table 9-21. Template Patterns for Date/Time Formatting
:
:
J Julian Day (days since January 1, 4712 BC)
I think 4712 should be 4713.
--
Tatsuo Ishii
---(end of broadcast)---
TIP 8: explain analyze is your friend
Merlin Moncure kirjutas E, 12.01.2004 kell 19:56:
Hannu Krosing wrote:
IIRC, the charset transformations are done as a separate step in the
wire protocol _before_ any parser has chance transform or not.
Yep. My point is that this is wrong.
Of course :)
We need this because our
the log on powergres.sra.co.jp, it turns out that
reverse look up for postgresql.org has been failed and this make it
impossible to receive those mails from postgresql.org.
Anyone can take care of this problem?
--
Tatsuo Ishii
---(end of broadcast
checking the log on powergres.sra.co.jp, it turns out that
reverse look up for postgresql.org has been failed and this make it
impossible to receive those mails from postgresql.org.
Anyone can take care of this problem?
--
Tatsuo Ishii
Here is the more detailed info:
It seems reverse look up
(AbstractJdbc1Statement.java:199)
at
org.postgresql.jdbc1.AbstractJdbc1Statement.executeUpdate(AbstractJdbc1Statement.java:183)
at test.main(test.java:10)
I'm not sure whether the JDBC driver or PostgreSQL backend should be
blamed though.
--
Tatsuo Ishii
Here is a test case:
create table daily_log
using
executeQuery works, but won't if there isn't a rule. Perhaps using plain
execute() would be the most appropriate thing to do.
Kris Jurka
Got it. With regard to this PostgreSQL JDBC driver confirms the JDBC
spec.
--
Tatsuo Ishii
---(end of broadcast
to make a back patch for
7.3-stable if nobody objects.
BTW, I'm interested in Korea PostgreSQL Users' Group since I myself am
a bord member of Japan PostgreSQL Users' Group. Please let me know if
both users group could make some collaboration, such as having a
seminar in Korea or in Japan.
--
Tatsuo
Tatsuo Ishii wrote:
It's surprising that nobody noticed the bug until now. It seems it has
been there since 7.3 days. I would like to make a back patch for
7.3-stable if nobody objects.
It's my bug :( -- sorry about that. Here's a 7.3 patch per Tom's nearby
advice. I'll apply if you'd
Has this been beaten to death now? Just curious if PITR was in Dev tree
yet. Been out of the loop. TIA.
I and my co workers are very interested in implementing PITR. We will
tackle this for 7.5 if no one objects.
--
Tatsuo Ishii
---(end of broadcast
I and some other developers are also interested in.
Do you think we can work together?
Sure. Why not. I think it would be practical to decide who is the
leader of this project, though.
--
Tatsuo Ishii
---(end of broadcast)---
TIP 1: subscribe
2.4.22+glibc 2.2.4+gcc 2.95...
--
Tatsuo Ishii
---(end of broadcast)---
TIP 8: explain analyze is your friend
.
This is not the first time tarballs have been streamlined. I'm glad I hadn't
built any RPMs yet.
Sigh. I'm very uncomfortable with the existence of two versions of
7.3.6. Also the fact that I cannot get the right tar ball till it is
copied to mirrors makes me uncomfortable too.
--
Tatsuo Ishii
If NOWAIT is the choice, I could live with it. If there's no
objection, I will go with NOWAIT, not NO WAIT.
--
Tatsuo Ishii
Tatsuo Ishii [EMAIL PROTECTED] writes:
LOCK TABLE table NO WAIT is OK for 7.5? If ok, I will make patches
against current with some docs changes.
Dept of minor
It seems NOWAIT is the winner...
--
Tatsuo Ishii
Oracle uses NOWAIT so we should go for that one.
Regards,
Hans
Tatsuo Ishii wrote:
If NOWAIT is the choice, I could live with it. If there's no
objection, I will go with NOWAIT, not NO WAIT.
--
Tatsuo
one checks my English grammer:-)
--
Tatsuo Ishii
It seems NOWAIT is the winner...
--
Tatsuo Ishii
Oracle uses NOWAIT so we should go for that one.
Regards,
Hans
Tatsuo Ishii wrote:
If NOWAIT is the choice, I could live with it. If there's
Tatsuo Ishii [EMAIL PROTECTED] writes:
Here is the patch I promised (against current).
This is missing the necessary adjustments in backend/nodes/ (copy and
equal funcs). Also the NOWAIT keyword must be added to the list of
nonreserved keywords near the bottom of gram.y.
Thanks
This is missing the necessary adjustments in backend/nodes/ (copy and
equal funcs). Also the NOWAIT keyword must be added to the list of
nonreserved keywords near the bottom of gram.y.
Thanks for the review. I'll work on this.
Here is the revised patch.
--
Tatsuo Ishii
of a mapping table between
storage size and terminal size for each encoding. Note that this
is not new problem, and sophiscated editors such as Emacs (mule) has
already concur that.
--
Tatsuo Ishii
---(end of broadcast)---
TIP 1: subscribe and unsubscribe
Dear Tatsuo,
Thanks for your reply, as I noticed from the source code that your name
often appears when dealing with multi-byte issues;-)
On Fri, 12 Mar 2004, Tatsuo Ishii wrote:
As far as I understand your code, it will be broken on many multi byte
encodings.
1) a character
and you can skip as
many characters as PQmnlen returns
5) goto 1) if any characters remain
~~of course this should be 2)
--
Tatsuo Ishii
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
, ok.
Thanks for you reply,
You are welcome!
--
Tatsuo Ishii
---(end of broadcast)---
TIP 8: explain analyze is your friend
Could you take a look at included screen shot?
I haven't found it. However I've made a little bit of trying with my
Oops. I have included this time.
Maybe you could point me some source of information about display lengths
of characters depending on the encoding?
I could write
checkpoint record. This may take considerable amount of
time, but still better than giving up recovery IMO. Any reason we
cannot do this?
--
Tatsuo Ishii
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
.
What's wrong with improving one of fragile parts of the system?
--
Tatsuo Ishii
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
just isn't an encoding.
Actually you can use UTF-8 instead of UNICODE when using
PostgreSQL. However the primary name is still UNICODE, and I agree
it's better to change to UTF-8 for the primary name. Maybe for 7.5?
--
Tatsuo Ishii
---(end of broadcast
in that it's
not multibyte ware.
I think we need to fix that as well.
--
Tatsuo Ishii
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister YourEmailAddressHere to [EMAIL PROTECTED])
no problem with
encoding itself.
--
Tatsuo Ishii
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
terminal encoding to E1, then SELECT
the table. Point is you do not use set client_encoding or \encoding
command. This will work as long as both E1 and E2 are single byte
encodings.
--
Tatsuo Ishii
---(end of broadcast)---
TIP 1: subscribe and unsubscribe
, like:
... WHERE field1 = _latin1'FooBar' and field2 = _utf8'Åäö'
In my understanding this was removed as of SQL:1999. I'm not sure
about SQL:2003 though.
--
Tatsuo Ishii
I can see that the lexer either needs to be taught about all the
different charsets or this is not going to work very
/pgpool/pgpool-1.2.2.tar.gz
--
Tatsuo Ishii
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
. This means that pgpool forces pgbench to
fallback to V2 protocol (remember that pgpool does not support V3
yet), and the start up packet flys on the wire twice at the each
connection statge. This actually makes the benchmark worse, still
pgpool is better than direct connection however.
--
Tatsuo
is nearly 10 times slower than UNIX socket. In the
function there are 2 read()s to process the startup packet. I think I
could enhance pool_read() so that it reduces the call to read() as
little as possible...
--
Tatsuo Ishii
---(end of broadcast)---
TIP 9
... IMO to justify those pains we need to give users
major enhancements. Honestly I don't understand why we should rush the
major version up.
--
Tatsuo Ishii
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
of
times when they ask me why SELECT returns results. If that kind of
wanings are installed, I think more Japanese users will be confused.
--
Tatsuo Ishii
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan
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.
--
Tatsuo Ishii
---(end of broadcast
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.
Right, and 7.5 will ship with tcp and localhost enabled
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
balancing, no failover.
I'm interested in if Slony-I solves all these bad. I will try it when
I have spare time.
--
Tatsuo Ishii
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's
to be.
Above looks quite true for me too.
--
Tatsuo Ishii
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
to be distributed as part of the
core?
At least in Japan PHP is much more popular than Python. If we have
plpython in core, I see no reason we do not have plPHP in core at
least from the popularity point of view.
--
Tatsuo Ishii
---(end of broadcast
to try -N option of pgbench. It avoids updates to
branches and tellers tables.
--
Tatsuo Ishii
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
The actual checking is done in INSERT/UPDATE/COPY. However, the
checking is currently very limited: every byte of a mutibyte character
must be greater than 0x7f.
Tatsuo,
do I understand correctly that there is no checking for
convertion between local charset and unicode in insert and
and
is correct from the standard's point of view...
--
Tatsuo Ishii
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister YourEmailAddressHere to [EMAIL PROTECTED])
I'm seeing this on my Linux box (kernel 2.4.18, glibc 2.2.4):
*** ./expected/horology.out Thu Sep 19 06:35:25 2002
--- ./results/horology.out Mon Oct 28 13:42:39 2002
***
*** 537,549
SELECT (timestamp with time zone 'today' = (timestamp with time zone 'tomorrow' -
I'm seeing this on my Linux box (kernel 2.4.18, glibc 2.2.4):
*** ./expected/horology.out Thu Sep 19 06:35:25 2002
--- ./results/horology.outMon Oct 28 13:42:39 2002
[snip]
Sorry, this must be due to summer time...
--
Tatsuo Ishii
---(end of broadcast
on Linux.
Define chinese. What character set for Chinese are you using?
--
Tatsuo Ishii
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
are in an
already-aborted transaction. Using a pg_conversion OID in stored rules
isn't very acceptable either.
Unfortunately, I don't see any way offhand to fix this without an
initdb :-(.
Sorry for the trouble and thanks for the fix.
--
Tatsuo Ishii
---(end of broadcast
will generate
src/backend/utils/mb/Unicode/utf8_to_gb18030.map
and
src/backend/utils/mb/Unicode/gb18030_to_utf8.map
(4) If they look good, rebuild PostgreSQL and test it.
--
Tatsuo Ishii
#! /usr/bin/perl
#
# Copyright 2002 by Bill Huang
#
# $Id: UCS_to_GB18030.pl,v 1.1 2002/06/13 08:28:55
Are we ready for RC1 yet?
I'm waiting for jenny wang confirms the fix regarding GB18030
support. In the mean time, I'll commit the fix anyway since current
GB183030 support is so badly broken (I have checked all regression
tests have passed).
--
Tatsuo Ishii
---(end
to turn on/off PREPARE/EXECUTE in pgbench so that we
could see how PRPARE/EXECUTE could improve the performance...
--
Tatsuo Ishii
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs
afraid adding that switch into the code may
make it messy.
But one of the purposes of pgbench is examining performance on
different environments, doesn't it? I'm afraid hard coded
PREPARE/EXECUTE makes it harder.
--
Tatsuo Ishii
---(end of broadcast
. If that happens, keeping that switch would help examining the
effect, no?
--
Tatsuo Ishii
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
was just concerned that having both in there would be a
maintenance headache and would perhaps double the amount of code and
make it complicated. Let see what the author does and we can decide
then.
Ok.
--
Tatsuo Ishii
---(end of broadcast
it quickly enough for reasonable performance will be worse. Keep
the problem out of the API and let each comparison function do what it
needs to do internally.
Agreed. That was the way I have been thinking about collation/create
character stuff too.
--
Tatsuo Ishii
---(end
.
Global symbol $setResult2 requires explicit package name at DBMirror.pl line 140.
Global symbol $setResult2 requires explicit package name at DBMirror.pl line 141.
Execution of DBMirror.pl aborted due to compilation errors.
This Linux and perl 5.6.1.
--
Tatsuo Ishii
---(end
What do the columns conforencoding and contoencoding refer to in
pg_conversion?
How would I convert those numbers to a string encoding name, just using SQL?
Chris
Use pg_encoding_to_char().
--
Tatsuo Ishii
---(end of broadcast)---
TIP 2
. It copies the input query and distribute
to multiple PostgreSQL servers. As long as one of a server is working,
users even do not notice some of them are failing.
--
Tatsuo Ishii
---(end of broadcast)---
TIP 2: you can get off all lists at once
)
transaction log based replications.
--
Tatsuo Ishii
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister YourEmailAddressHere to [EMAIL PROTECTED])
The error message says all. You are trying to insert a character which
is not a UTF-8. Probably you are inputting UCS-2?
--
Tatsuo Ishii
From: Atahualpa Jones [EMAIL PROTECTED]
Subject: Postgresql, unicode and umlauts
Date: Wed, 1 Jan 2003 20:17:15 +0100
Message-ID: 000d01c2b1ca$67838d60
I noticed sync() is used in PostgreSQL.
CHECKPOINT - FlushBufferPool() - smgrsync() - mdsync() - sync()
Can someone tell me why we need sync() here?
--
Tatsuo Ishii
---(end of broadcast)---
TIP 2: you can get off all lists at once
Tatsuo Ishii wrote:
I noticed sync() is used in PostgreSQL.
CHECKPOINT - FlushBufferPool() - smgrsync() - mdsync() - sync()
Can someone tell me why we need sync() here?
As part of checkpoint, we discard some WAL files. To do that, we must
first be sure that all the dirty buffers
to disk *and* wait till they're written. But sync() and sleep
for awhile is the closest portable approximation.
Are you saying that fsync() might not wait untill the IO completes?
--
Tatsuo Ishii
---(end of broadcast)---
TIP 5: Have you checked our
scheduled, is not necessarily complete upon
return from sync.
I'm just wondering why we do not use fsync() to flush data/index
pages.
--
Tatsuo Ishii
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http
Tatsuo Ishii [EMAIL PROTECTED] writes:
I'm just wondering why we do not use fsync() to flush data/index
pages.
There isn't any efficient way to do that AFAICS. The process that wants
to do the checkpoint hasn't got any way to know just which files need to
be sync'd. Even if it did know
that is ideal.
(Yes, I should try this myself...)
Ignored as in 'passed through unchanged'; or ignored as in 'removed from
the string'?
removed from the string. BTW, if I remember correctly, the euro sign is
supported in ISO-8859-16, not in ISO-8859-1.
--
Tatsuo Ishii
a little bit inconsistent...
--
Tatsuo Ishii
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
. Try re-initdb with --no-locale
option to disable the locale support. Unfortunately there's no way to
build PostgreSQL 7.3 or later without locale support except specify
the option at initdb time.
--
Tatsuo Ishii
---(end of broadcast)---
TIP 3
) characters?
--
Tatsuo Ishii
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
, getdatabaseencoding() is called. This is simply
wrong since it does not return the client encoding specified by
postgressql.conf's client_encoding directive. Instead
pg_client_encoding() should be called. (fix to this is included in the
patches)
--
Tatsuo Ishii
have passed on my Linux
box.
--
Tatsuo Ishii
--- cut here -
*** postgresql-7.3.1/src/backend/regex/regcomp.c.orig 2002-09-05 05:31:24.0
+0900
--- postgresql-7.3.1/src/backend/regex/regcomp.c2003-02-05 10:05
just committed into the 7.3 stable branch.
--
Tatsuo Ishii
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
all possible
regex patterns.
--
Tatsuo Ishii
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
ISO-8859-1 can be encoded in either 7 bit or 8 bit(we use
this). I don't know what it is called though.
--
Tatsuo Ishii
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
to natively support UTF-16.
--
Tatsuo Ishii
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
software and lower the max connections.
--
Tatsuo Ishii
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister YourEmailAddressHere to [EMAIL PROTECTED])
be possible that
the file system type might affect the wal_sync choice.
--
Tatsuo Ishii
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get
/utils/mb/Unicode/
and rebuild postgres to use them, then I can test this out locally.
Just edit src/backend/utils/mb/Unicode/*.map and rebiuld
PostgreSQL. Probably you might want to modify utf8_to_euc_jp.map and
euc_jp_to_utf8.map.
--
Tatsuo Ishii
---(end of broadcast
made clean
explanation why non-repeatable results happen...
--
Tatsuo Ishii
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
performance
degration! I guess this is due to the poor design of bufmgr. Until it
is fixed, just increasing the number of shared_buffers a bit, say
1024, is enough IMHO.
--
Tatsuo Ishii
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
the connection. This is just a
mistake.
I think we could fix 1) without any backward compatibilty problem and
should be applied to both 7.3-STATBLE and current.
--
Tatsuo Ishii
---(end of broadcast)---
TIP 2: you can get off all lists at once
database_encoding?
Why? No matter how the backend's behavior regarding client_encoding
changes, libpq won't be affected by it since 7.2 and 7.3 libpq does
not use client_encoding anyway.
--
Tatsuo Ishii
---(end of broadcast)---
TIP 5: Have you
. pg_client_encoding() returns the
client encoding as expected. Client/database encoding conversion
will be peformed.
After changes: same as above.
--
Tatsuo Ishii
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http
that Cygwin port of PostgreSQL does not pass his test
neither.
--
Tatsuo Ishii
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
.
--
Tatsuo Ishii
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
to open files in the buffer manager?
If so, basically PostgreSQL uses open() with flags (O_RDWR |
PG_BINARY, 0600).
--
Tatsuo Ishii
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
did not mention it explicitly. I meant we use the same
implementation as Jan's work. He uses open()+_commit(), I believe.
--
Tatsuo Ishii
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
.
I regard the difference between sync() and fsync() does not affect too
much to the whole performance. Checkpoint process is performed as a
separate process and the fsync() part of checkpoint does nothing with
WAL, that means other backend processes, busy with WAL IO will
not be bothered.
--
Tatsuo
with the transaction log files. So probably I think I should stick
with open()+_commit() approach for ordinary table/index files too.
--
Tatsuo Ishii
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe
Sample Code
insert into t2 (names) values ('xxx');
What did you insert as xxx? I would like to see them as hex or octal
value.
--
Tatsuo Ishii
As 'xxx' I insert Cyrillic characters. Here are some hex values: E0, FE,
DE, EE.
Are you sure that these are correct UTF-8 character
Can someone please fix this? Building JDBC staffs in current has been
broken for a while(7.2.x is ok). Maybe current JDBC build process
requires more recent version of ant than I have, I don't know. But if
so, that should be stated somewhere in the docs explicitly, I think.
/usr/bin/ant
Can someone who is multbyte-aware comment on this patch? Thanks.
I thought the patch is not relevant to multibyte support?
--
Tatsuo Ishii
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send
Whatever you do with this patch, remember that the USE_LOCALE symbol is
gone.
I thought we have some way to tern off locale support at the configure
time.
--
Tatsuo Ishii
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
I'm about to commit your patches with a small fix.
--
Tatsuo Ishii
From: Joe Conway [EMAIL PROTECTED]
Subject: Re: [PATCHES] unknownin/out patch (was [HACKERS] PQescapeBytea is
Date: Mon, 08 Apr 2002 22:57:47 -0700
Message-ID: [EMAIL PROTECTED]
Joe Conway wrote:
Tatsuo Ishii wrote
1 - 100 of 1614 matches
Mail list logo
