[BUGS] BUG #7914: pg_dump aborts occasionally

2013-03-04 Thread s-morita
The following bug has been logged on the website: Bug reference: 7914 Logged by: Shin-ichi MORITA Email address: s-mor...@beingcorp.co.jp PostgreSQL version: 8.4.16 Operating system: Windows Server 2012 Description: Hi great team, I encountered a strange error during

Re: [BUGS] Excessive space allocations in Postgresql 9.1.6 system files causing the file system to run out of space.

2013-03-04 Thread fburgess
Does anyone know, what the names/location of the pg_upgrade cleanup scripts? We upgraded from 8.4.3 to 9.1.6 on linux   thanks   Original Message Subject: Re: [BUGS] Excessive space allocations in Postgresql 9.1.6system files causing the file system to run out of space.From: Kev

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

2013-03-04 Thread Tom Lane
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 Hm.

[BUGS] BUG #7916: memory leak with array_agg

2013-03-04 Thread eshkinkot
The following bug has been logged on the website: Bug reference: 7916 Logged by: Sergey Burladyan Email address: eshkin...@gmail.com PostgreSQL version: 9.2.3 Operating system: Debian GNU/Linux 7.0 (wheezy) Description: Looks like array_agg have memory leak. In my exa

[BUGS] BUG #7915: problema con postgis 2.0

2013-03-04 Thread gloria . evelis
The following bug has been logged on the website: Bug reference: 7915 Logged by: Gloria Valladares Email address: gloria.eve...@gmail.com PostgreSQL version: 9.1.6 Operating system: ubuntu 12.04 Description: Tengo problemas con los datos te tenia en postgres 9.0 con p

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

2013-03-04 Thread Euler Taveira
On 03-03-2013 12:42, Tom Lane wrote: > Anybody have an opinion on whether to back-patch such a fix? It seems > conceivable that somebody out there is relying on the current behavior. > OTOH, I believe that only Turkish UTF8 locales exhibit this behavior > (the single-byte-encoding code path in str