t;
> These characters have '\'(0x5c) in low byte of 2 Bytes.
Please send reproducible input pattern.
I saw expected results as long as client encoding is set to SJIS:
postgres=# \encoding SJIS
postgres=# SELECT '表' AS "ソ";
ソ
表
(1 行)
--
Itagaki Taka
On Wed, Sep 28, 2011 at 11:05, Tom Lane wrote:
> "Itagaki Takahiro" writes:
>> Our documentation says OIDS and HEADER options in COPY command take [
>> boolean ] arguments, but actually they don't accept any arguments. We can
>> only set them to TRUE by s
The following bug has been logged online:
Bug reference: 6227
Logged by: Itagaki Takahiro
Email address: itagaki.takah...@gmail.com
PostgreSQL version: 9.1 and all
Operating system: N/A
Description:No arguments for COPY OIDS and HEADER
Details:
Our documentation
The following bug has been logged online:
Bug reference: 6181
Logged by: Itagaki Takahiro
Email address: itagaki.takah...@gmail.com
PostgreSQL version: 9.1 RC1 (x86)
Operating system: Windows 7 (64bit)
Description:concat_ws() incompatibility with MySQL
Details:
For
only expected standard pgbench transactions.
Since they are short enough, the difference should not be large.
If you have a plan to execute custom queries that take 1 second
or more, a hard cut-off makes senses.
--
Itagaki Takahiro
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresq
is just broken or behaves
undesirable as a feature. When I created english locale on Windows,
it returnes expected results in both cases.
Personally, I don't trust locale functions in libc on Linux platforms...
--
Itagaki Takahiro
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresq
lc_collate".
Your locale seems to just ignore symbol characters.
I have an expected result at least in C locale.
--
Itagaki Takahiro
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
es just supports one of them. I think it won't be changed in the near
term. So, you would need to define a CONVERSION for your purpose as of now.
However, I think we could have an extension of conversion procedure set
for Japanese confused encodings out of the core.
--
Itagaki Takahiro
--
On Wed, Mar 23, 2011 at 13:02, Tatsuo Ishii wrote:
> I think what we can do best here is, adding new encoding and default
> conversion.
Agreed if the encoding is added as an user-defined encoding.
I don't want to add built-in encodings only for Japanese language any more.
--
Itaga
in the near term for unicode
Emoji issue.
--
Itagaki Takahiro
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
encoding names and define
the above conversion procs as the default:
=# CREATE ENCODING eucjp_relaxed;
=# CREATE DEFAULT CONVERSION xxx FOR utf8 TO eucjp_relaxed
FROM utf8_to_eucjp_relaxed;
I think overhaul of conversion support is a TODO item.
--
Itagaki Takahiro
--
Sent via
sult, only one row appears in table a, although two should be
> there...
It should be not a bug.
You probably need to define f2 as "returns SETOF void" function.
--
Itagaki Takahiro
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
0 | |
| | | 9187201950435737471 |
9187201950435737471 | 9187201950435737471 | 9187201950435737471
(2 rows)
--
Itagaki Takahiro
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
e assertion failure.
It looks we call CreatePortal for ROLLBACK, but don't invoke
DropPortal nor AtAbort_Portals before AtCleanup_Portals.
--
Itagaki Takahiro
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
k the string-comparison is unreliable. So, I'd like to replace
the code to use PQtransactionStatus(). I have two patches to do it:
The first one (ecpg-trans-quick_20101014.patch) is a quick fix
that replaces only the above test.
The second one (ecpg-trans-full_20101014.patch) replaces all of
struc
ks on 8.3, but it's still broken. Here is the code in 8.3.
It ignores "ROLLBACK TO savepoint", but also ignores "ROLLBACK TRANSACTION".
if (strcmp(transaction, "commit") == 0 || strcmp(transaction, "rollback") == 0)
con->committed = true;
e
bug report!
Fixed and backpatched to 8.3.
--
Itagaki Takahiro
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
ep 27, 2010 at 11:14 PM, Tom Lane wrote:
> I think this is a Microsoft bug and it's their problem to fix, not ours.
OK, but bad news is that the bug is in VC 2008, but they have not
fixed it even in VC 2010. I'm not sure they will fix it in the future...
--
Itagaki Takahiro
--
Sent
On Fri, Sep 24, 2010 at 3:01 PM, Itagaki Takahiro
wrote:
> Windows 7 supports symbolic links like UNIX,
> but initdb cannot initialize a database cluster
> if the path (-D) contains symlinks.
The bug might come from the following bug by Microsoft:
http://connect.microsoft.com/Vis
-bit
> (1 row)
>
> got f,t
> expected t,f
> hope the problem is clear
I found 9.0 and 9.1dev returns t,f as expected.
Is it an incompatibility between 8.4 and 9.0?
--
Itagaki Takahiro
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
The following bug has been logged online:
Bug reference: 5674
Logged by: Itagaki Takahiro
Email address: itagaki.takah...@gmail.com
PostgreSQL version: 9.0.0 (32bit)
Operating system: Windows 7 (64bit)
Description:initdb failed if path contains symlink
Details
start.
Unfortunately, effective_io_concurrency is not supported on Windows.
It works on Linux and UNIXes, but must be 1 on Windows.
--
Itagaki Takahiro
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
f there are any old server processes still running,
and terminate them.
Changes for the issue might be introduced between 8.2 and 8.3,
or in bugfixes only applied to 8.3 or newer versions.
--
Itagaki Takahiro
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To mak
On Tue, Aug 24, 2010 at 9:45 AM, Tom Lane wrote:
> "Itagaki Takahiro" writes:
>> 9.0beta4 seems to fail automatic crash recovery after
>> some of backend processes crashed,
>
> Works for me, and always has worked for me (and I crash backend
> processes regularly
The following bug has been logged online:
Bug reference: 5628
Logged by: Itagaki Takahiro
Email address: itagaki.takah...@gmail.com
PostgreSQL version: 9.0b4 (32bit)
Operating system: Windows 7 (64bit)
Description:9.0beta4 failed automatic crash recovery
Details
he near-term fix; it adds ALLOCSET_DEFAULT_INITSIZE
bytes to memory assumption.
We might need the same adjustment for string_agg(), that consumes
1024 bytes for the transit condition. array_agg() and string_agg()
are only aggregates that have "internal" for aggtranstype.
The following bug has been logged online:
Bug reference: 5608
Logged by: Itagaki Takahiro
Email address: itagaki.takah...@gmail.com
PostgreSQL version: 9.0beta4
Operating system: Windows 7 (32bit)
Description:array_agg() consumes too much memory
Details:
I
Alvaro Herrera wrote:
> So I'm going to apply your patch to both 8.4 and HEAD; we can always
> improve it later, I guess.
Thank you for your applying.
I think the fix is ugly, too. We need to introduce cleaner solution for 8.5.
Regards,
---
ITAGAKI Takahiro
NTT Open Source Soft
The following bug has been logged online:
Bug reference: 5016
Logged by: Itagaki Takahiro
Email address: itagaki.takah...@oss.ntt.co.jp
PostgreSQL version: 8.5 Alpha 1
Operating system: Windows XP (mingw)
Description:dlltool error in libecpg_compatdll.def
Details
threshold = 10);
AutoVacOpts.vacuum_threshold should be 10 (comes from reloptions),
but AutoVacOpts.vacuum_scale_factor should be (comes from GUC).
If we use boolean flags, we need booleans for each fields in AutoVacOpts.
(vacuum_threshold_is_default, vacuum_scale_factor_is_default, ...)
Regards,
---
ITAGAKI Takahiro
N
eloptions. Is it possible to change the default values of reloptions
> to some magic number (-1 or so) ?
Regards,
---
ITAGAKI Takahiro
NTT Open Source Software Center
fix-relopts-20090820.patch
Description: Binary data
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
ed or not independntly.
Regards,
---
ITAGAKI Takahiro
NTT Open Source Software Center
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
ix it?
Regards,
---
ITAGAKI Takahiro
NTT Open Source Software Center
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
in postmaster;
There are no chance to see uninitialized state of 'pgss' after relasing
AddinShmemInitLock and before load dumpfile into it.
I also check pgss_shmem_shutdown and no problem.
It is called only once from postmaster on shutdown.
Regards,
---
ITAGAKI Takahiro
NTT Ope
LWLockAcquire(AddinShmemInitLock, LW_EXCLUSIVE);
pgss = ShmemInitStruct("pg_stat_statements" &found);
if (!found)
{
[Initialize shared memory];
[Read dumpfile];
}
LWLockRelease(AddinShmemInitLock);
}
Regards,
---
ITAGAKI
uot;user" to text type.
=# select * from t where str in (user::text, 'abc...ijk');
The result might be a designed behavior, but is very surprising.
What should we care for it?
Regards,
---
ITAGAKI Takahiro
NTT Open Source Software Center
--
Sent via pgsql-bugs mailing list (pgsql
ding=UTF8 --locale="Chinese (Simplified)"
Regards,
---
ITAGAKI Takahiro
NTT Open Source Software Center
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
The following bug has been logged online:
Bug reference: 4845
Logged by: Itagaki Takahiro
Email address: itagaki.takah...@oss.ntt.co.jp
PostgreSQL version: 8.4dev, 8.3.7
Operating system: Windows XP
Description:cash_in is broken for lc_monetary = 'ja'
Deta
element,
xmlattributes (1 as one, 'deuce' as two, '<>&"''' as three),
'content', '<>&"''');
xmlelement
The following bug has been logged online:
Bug reference: 4822
Logged by: Itagaki Takahiro
Email address: itagaki.takah...@oss.ntt.co.jp
PostgreSQL version: 8.4dev
Operating system: Linux, Windows
Description:xmlattributes encodes '&' twice
Detail
The following bug has been logged online:
Bug reference: 4660
Logged by: ITAGAKI Takahiro
Email address: itagaki.takah...@oss.ntt.co.jp
PostgreSQL version: 8.3.3
Operating system: Fedora 8
Description:float functions return -0
Details:
Float8 versions of trunc
Tom Lane <[EMAIL PROTECTED]> wrote:
> ITAGAKI Takahiro <[EMAIL PROTECTED]> writes:
> > We probably need to add PG_BINARY when we open control files
> > because 0x1A is an end-of-file marker on Windows.
>
> Well, why is that a bug? If the platform is so silly a
@@
char *buffer;
pg_crc32crc;
- if ((fd = open(XLOG_CONTROL_FILE, O_RDONLY, 0)) < 0)
+ if ((fd = open(XLOG_CONTROL_FILE, O_RDONLY | PG_BINARY, 0)) < 0)
{
/*
* If pg_control is not there at all, or we can't
-
Aggregate (cost=20.81..20.81 rows=1 width=82)
Output: max(item1), max((item2)::text)
-> Seq Scan on b (cost=0.00..17.20 rows=720 width=82)
Output: item1, item2
(4 rows)
Regards,
---
ITAGAKI Takahiro
NTT Open Source Software Center
--
Sent via pgsql-bugs mailing list (pg
cur.execute("create table ph2 (nm varchar, ph varchar)")
conn.commit()
>print "table created."
An auto-commit feature is initially off on databases supporting
transactions. See http://www.python.org/dev/peps/pep-0249/ .
Regards,
---
ITAGAKI Takahiro
"ITAGAKI Takahiro" <[EMAIL PROTECTED]> wrote:
> Bug reference: 3969
> Description:pg_ctl cannot detect server startup
> Details:
> pg_ctl -w -o "-p 5432 -c max_connections=100" start
> waits for server startup forever and timeout,
> but
The following bug has been logged online:
Bug reference: 3969
Logged by: ITAGAKI Takahiro
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.6, 8.3.0
Operating system: CentOS 5, Windows XP
Description:pg_ctl cannot detect server startup
Details:
pg_ctl -w -o
Tom Lane <[EMAIL PROTECTED]> wrote:
> "ITAGAKI Takahiro" <[EMAIL PROTECTED]> writes:
> > All of filler fields in branches, tellers and history is NULL. It is
> > probabbly a mistake because there are fields of char(22-88) in the table
> > definitions
The following bug has been logged online:
Bug reference: 3681
Logged by: ITAGAKI Takahiro
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.5, 8.3beta1
Operating system: independent
Description:fillers are NULL in pgbench
Details:
All of filler fields in
The following bug has been logged online:
Bug reference: 3674
Logged by: ITAGAKI Takahiro
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3beta1
Operating system: independent
Description:Unnecessary checkpoints by WAL Writer
Details:
WAL Writer requests
The following bug has been logged online:
Bug reference: 3622
Logged by: ITAGAKI Takahiro
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3dev
Operating system: ALL
Description:pg_rotate_logfile() does not work
Details:
"SELECT pg_rotate_logfile()"
The following bug has been logged online:
Bug reference: 3621
Logged by: ITAGAKI Takahiro
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3dev
Operating system: Windows
Description:Syslogger will not start
Details:
Syslogger will not start because of the
escription:Error on COPY TO/FROM 'non-ascii-path'
> > When I set postgres a different character encoding from OS, COPY TO/FROM
> > 'non-ascii-path' cannot open the path.
Regards,
---
ITAGAKI Takahiro
NTT Open Source Software Center
The following bug has been logged online:
Bug reference: 3453
Logged by: ITAGAKI Takahiro
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2, 8.3dev
Operating system: independent (especially Windows)
Description:Error on COPY TO/FROM 'non-ascii-path
54 matches
Mail list logo
