[BUGS] BUG #7917: Error while migrating data

2013-03-05 Thread renjith . pt
The following bug has been logged on the website: Bug reference: 7917 Logged by: Renjith Email address: renjith...@galfar.com PostgreSQL version: 9.1.0 Operating system: Centos Description: I using one application alfresco with postgresql 9.1. it throws error once dat

Re: [BUGS] BUG #7914: pg_dump aborts occasionally

2013-03-05 Thread Shin-ichi MORITA
Hi Tom, s-mor...@beingcorp.co.jp writes: I encountered a strange error during pg_dump as below: pg_dump: Dumping the contents of table "t_file_data" failed: PQgetCopyData() failed. pg_dump: Error message from server: lost synchronization with server: got message type "d", length 21861

Re: [BUGS] BUG #7913: TO_CHAR Function & Turkish collate

2013-03-05 Thread Tom Lane
Euler Taveira writes: > As you suggested, s/str_toupper/pg_toupper/ in the else block (no TM) is the > right fix. I'm not aware of another locale that would break if we apply such a > change in a stable branch. Are you want me to post a fix? Thanks, but I have a fix mostly written already.

Re: [BUGS] BUG #7913: TO_CHAR Function & Turkish collate

2013-03-05 Thread Tom Lane
Peter Eisentraut writes: > On Sun, 2013-03-03 at 10:42 -0500, Tom Lane wrote: >> Anybody have an opinion on whether to back-patch such a fix? > I think it's a bug that should be backpatched. Done. In addition to day/month names, I found that there were case-folding hazards for timezone abbrevia

Re: [BUGS] BUG #7914: pg_dump aborts occasionally

2013-03-05 Thread Tom Lane
"Shin-ichi MORITA" writes: > Hi Tom, >> Hm. Can you create a reproducible test case for this? > I think this issue happens when pg_dump is slower than the backend > for some reason. If so, perhaps injecting a sleep() delay into the right place in pg_dump or libpq would make it reproducible? I

Re: [BUGS] BUG #7916: memory leak with array_agg

2013-03-05 Thread Tom Lane
eshkin...@gmail.com writes: > Looks like array_agg have memory leak. In my example it eat 3 Gb RSS, but > equal user defined aggregate > created by myself use only 7Mb RSS. AFAICT there's no actual leak here; array_agg is just optimized for speed rather than space. It eats about 8K per hashtable

Re: [BUGS] BUG #7916: memory leak with array_agg

2013-03-05 Thread Sergey Burladyan
Tom Lane writes: > AFAICT there's no actual leak here; array_agg is just optimized for > speed rather than space. It eats about 8K per hashtable entry. > While the planner knows that, it's got no good idea how many groups > will be produced by the query, so it underestimates the space needed > -

[BUGS] BUG #7918: limitation of pagination with LIMIT and OFFSET

2013-03-05 Thread adrianopatrick
The following bug has been logged on the website: Bug reference: 7918 Logged by: Adriano Patrick do Nascimento Cunha Email address: adrianopatr...@gmail.com PostgreSQL version: 8.4.7 Operating system: Windows/Linux Description: Hello guys, today I need to process a qu