[SPAM?]Re: [BUGS] BUG #5089: not supported plpsql

2009-10-02 Thread Robert Haas
On Wed, Sep 30, 2009 at 4:33 AM, Yamashkin Alex wrote: > > The following bug has been logged online: > > Bug reference:      5089 > Logged by:          Yamashkin Alex > Email address:      defa...@smart-soft.ru > PostgreSQL version: 8.4.0.1 > Operating system:   windows XP Embeded > Description:  

Re: [BUGS] BUG #5089: not supported plpsql

2009-10-02 Thread Robert Haas
On Wed, Sep 30, 2009 at 4:33 AM, Yamashkin Alex wrote: > > The following bug has been logged online: > > Bug reference:      5089 > Logged by:          Yamashkin Alex > Email address:      defa...@smart-soft.ru > PostgreSQL version: 8.4.0.1 > Operating system:   windows XP Embeded > Description:  

Re: [BUGS] BUG #5095: pg_statio_xxx_sequences does not work

2009-10-02 Thread Tom Lane
"Akira Kurosawa" writes: > This problem happens because "pgstat_info" was not initialized in the > function > "pgstat_initstats" when relkind = 'S'. (pgstat_info = NULL). Looks like my oversight :-(. Patch applied, thanks for the report! Interestingly, it seems that this causes nextval() to con

Re: [BUGS] BUG #5090: erro

2009-10-02 Thread Robert Haas
On Wed, Sep 30, 2009 at 7:11 AM, Edinei wrote: > > The following bug has been logged online: > > Bug reference:      5090 > Logged by:          Edinei > Email address:      edi...@guaporepecuaria.com.br > PostgreSQL version: 8.4 > Operating system:   Windows XP > Description:        erro > Details

Re: [BUGS] BUG #5093: Prepared query gives different PGresult than exec'd equivalent

2009-10-02 Thread Tom Lane
"Mike Pomraning" writes: > The following short program installs a RULE to SELECT two rows INSTEAD of > INSERTing into a VIEW. > When it PQexec's the insertion, I get a PGresult object with PQntuples == 2. > However, when it PREPAREs/EXECUTEs the very same SQL, the PGresult has > PQntuples == 0.

Re: [BUGS] BUG #5094: bad result in dblink_get_result when async command sending

2009-10-02 Thread Tom Lane
"Sergey Tomoulevitch" writes: > When I send command in async query, eq: > SELECT dblink_send_query('remoteconn', 'INSERT INTO mytable (f1, f2) VALUES > (1,2);'); > I can not get result for this, eq: > SELECT dblink_get_result('remoteconn'); > I got error "ERRCODE_DATATYPE_MISMATCH". I'm not s

[BUGS] BUG #5094: bad result in dblink_get_result when async command sending

2009-10-02 Thread Sergey Tomoulevitch
The following bug has been logged online: Bug reference: 5094 Logged by: Sergey Tomoulevitch Email address: phoinix.pub...@gmail.com PostgreSQL version: 8.4 Operating system: any Description:bad result in dblink_get_result when async command sending Details: Good da

[BUGS] BUG #5093: Prepared query gives different PGresult than exec'd equivalent

2009-10-02 Thread Mike Pomraning
The following bug has been logged online: Bug reference: 5093 Logged by: Mike Pomraning Email address: m...@pilcrow.madison.wi.us PostgreSQL version: 8.4.1 Operating system: Linux i686 2.6.18-128.7.1.el5 Description:Prepared query gives different PGresult than exec'd

[BUGS] BUG #5095: pg_statio_xxx_sequences does not work

2009-10-02 Thread Akira Kurosawa
The following bug has been logged online: Bug reference: 5095 Logged by: Akira Kurosawa Email address: kurosawa-ak...@mxc.nes.nec.co.jp PostgreSQL version: 8.3.5, 8.4.1 Operating system: Red Hat EL 5 Description:pg_statio_xxx_sequences does not work Details: I found

Re: [BUGS] BUG #5092: to_ascii(); ascii() don't work with bytea

2009-10-02 Thread Peter Eisentraut
On Fri, 2009-10-02 at 02:17 +, Dan French wrote: > #1: bytea_string = '"0"' (table; bytea) > Function: >trim('"' both from bytea_string) > fails and returns: '"0' Works for me. Please submit a complete test case. > #2: Come on folks: Bytea is a series of bytes. Conversion to ASCII is