Re: [BUGS] BUG #5487: dblink failed with 63 bytes connection names

"Takahiro Itagaki" wrote: > Bug reference: 5487 > Logged by: Takahiro Itagaki > Email address: itagaki.takah...@oss.ntt.co.jp > Description:dblink failed with 63 bytes connection names > Details: > > Contib/dblink module seems to have

[BUGS] BUG #5487: dblink failed with 63 bytes connection names

The following bug has been logged online: Bug reference: 5487 Logged by: Takahiro Itagaki Email address: itagaki.takah...@oss.ntt.co.jp PostgreSQL version: 9.0beta1 Operating system: Linux Description:dblink failed with 63 bytes connection names Details: Contib

[BUGS] BUG #5458: Permission check is skipped by inheritance

The following bug has been logged online: Bug reference: 5458 Logged by: Takahiro Itagaki Email address: itagaki.takah...@oss.ntt.co.jp PostgreSQL version: 9.0beta1 Operating system: Linux (maybe ALL) Description:Permission check is skipped by inheritance Details

Re: [HACKERS] [BUGS] "SET search_path" clause ignored during function creation

Tom Lane wrote: > Takahiro Itagaki writes: > > Thanks for the report! Please check whether the attached patch > > is the correct fix. An additional regression test is included. > > That's going to provoke "uninitialized variable" compiler warnings, >

Re: [BUGS] "SET search_path" clause ignored during function creation

ath" an _not_ with the current > search path at the time pof creation. Thanks for the report! Please check whether the attached patch is the correct fix. An additional regression test is included. Regards, --- Takahiro Itagaki NTT Open Source Software Center create_function_with_sear

Re: [BUGS] BUG #5450: system lacked sufficient buffer space, or because a queue was full, could not perform the operation

ating system: Window xp(sp2) > > > > BTW, your message comes from WSAENOBUFS (10055). The error could be > > raised by various reasons. We need what you did when you receive > > the message to research your problem. Regards, --- Takahiro Itagaki NTT Open Source S

Re: [BUGS] BUG #5450: system lacked sufficient buffer space, or because a queue was full, could not perform the operation

EOF on client connection > 2010-04-20 00:55:47 LOG: could not receive data from client: the system > lacked sufficient buffer space, or because a queue was full, could not > perform the operation on a socket. Regards, --- Takahiro Itagaki NTT Open Source Software Center -- Sent

Re: [BUGS] BUG #5438: Bug/quirk in ascii() function

tabases if you define a char version of ascii(). =# CREATE FUNCTION ascii(bpchar) RETURNS integer AS 'ascii' LANGUAGE internal; =# SELECT ascii(cast(' ' as char(1))); ascii --- 32 (1 row) Do you know how the SQL standard mention the behavior? IMHO, postgres' behavior

Re: [BUGS] BUG #5398: psql gives syntax error on .sql files with UTF-8 BOM

ot;, the syntax error is removed. It will be improved in 9.0, the next release. Ignore leading UTF-8-encoded Unicode byte-order marker in psql http://developer.postgresql.org/pgdocs/postgres/release-9-0.html#AEN98917 Regards, --- Takahiro Itagaki NTT Open Source Software Center -- Sent via pgsql

Re: [BUGS] BUG #5394: invalid declspec for PG_MODULE_MAGIC

T" might be arguable. Regards, --- Takahiro Itagaki NTT Open Source Software Center PGMODULEEXPORT.patch Description: Binary data -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs

Re: [BUGS] UTF-8 encoding failure

UTF-8 codepage cannot display any kanji characters. I'm not sure what we can do to fix it ... some font settings in the registory? Regards, --- Takahiro Itagaki 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

Re: [BUGS] BUG #5326: The 2nd update of a table which has foreign keys is blocked.

f so, can we add a "has_deferred_FKs()" check to the condition? if ((!has_deferred_FKs(rel) || !TransactionIdIsCurrentTransactionId(...)) && RI_FKey_keyequal_upd_fk(...) Regards, --- Takahiro Itagaki 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

Re: [BUGS] Concurrent update failure in HEAD

Tom Lane wrote: > Takahiro Itagaki writes: > > I found pgbench sometimes receives responces of "UPDATE 0" from HEAD server. > > When I re-tested pgbench with 8.4.2 server, all of the results were "UPDATE > > 1". > > Are there known issues in

[BUGS] Concurrent update failure in HEAD

ench. There were differences in 'calls' and 'rows' fields in it, but it should be same because pgbench always updates a row per query. Regards, --- Takahiro Itagaki NTT Open Source Software Center pgbench_debug.patch Description: Binary data -- Sent via pgsql-bugs m