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
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
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
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
"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
"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.
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
"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
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:
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:
10 matches
Mail list logo