On 14/10/10 12:14, Itagaki Takahiro wrote:
Which solution is better? Or, another idea?
This does seem to be an new bug in previously working code. While any solution that fixes the problem is good, it might pay to look the code that worked before. As reported, it worked for ecpg (PostgreSQL 8.3.8) 4.4.1.
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
