johnb | 12 Mar 06:40 2015
Picon

BUG #12854: PG Admin 3 Restore/Import Button

The following bug has been logged on the website:

Bug reference:      12854
Logged by:          John Banfield
Email address:      johnb <at> drsmash.co.za
PostgreSQL version: 9.3.0
Operating system:   Windows 7
Description:        

I support multiple Postgres data bases using PGAdmin3, 1.18.1 
Have never had a problem and feel its a good tool (when you get to know it)
I use PGAdmin3 to backup my users data (Custom)
I then remove all files from my own data base
And then Import the backup, this has always worked

My Problem is the Restore/Import Button is now disabled
This is on all the data bases so I feel it must be a PGAdmin setting 
My pg_hba.conf  have not changed or the databases
# IPv4 local connections:
host all all 127.0.0.1/32 trust
host all all 0.0.0.0/0 trust
# IPv6 local connections:
host all all ::1/128  md5

I can find no help to resolve this problem surfing although others have had
this problem
I have reinstalled PGAdmin with no effect and it appeared to inherited all
my databases that I used

Please can you help me, Thanks John
(Continue reading)

Ronan Dunklau | 12 Mar 10:39 2015

PGDump / copy bugs with "big lines" ?

Hello.

The documentation mentions the following limits for sizes:

Maximum Field Size      1 GB
Maximum Row Size        1.6 TB

However, it seems like rows bigger than 1GB can't be COPYed out:

ro=# create table test_text (c1 text, c2 text);
CREATE TABLE
ro=# insert into test_text (c1) VALUES (repeat('a', 536870912));
INSERT 0 1
ro=# update test_text set c2 = c1;
UPDATE 1

Then, trying to dump or copy that results in the following error:

ro=# COPY test_text TO '/tmp/test';
ERROR:  out of memory
DÉTAIL : Cannot enlarge string buffer containing 536870913 bytes by 536870912 
more bytes.

In fact, the same thing happens when using a dumb SELECT:

ro=# select * from test_text ;
ERROR:  out of memory
DÉTAIL : Cannot enlarge string buffer containing 536870922 bytes by 536870912 
more bytes.

(Continue reading)

m40636067 | 12 Mar 04:22 2015
Picon

BUG #12853: Cannot install

The following bug has been logged on the website:

Bug reference:      12853
Logged by:          Brian
Email address:      m40636067 <at> gmail.com
PostgreSQL version: 9.4.1
Operating system:   W2K3 Server 32x
Description:        

Tried to install "http://www.postgresql.org/download/windows" but got this
error: 
There has been an error.
Unknown error while running c:\documents and settings\administrator\Local
Settings\Temp\1\postgressql_intaller_230fad1713\getlocales.exe

--

-- 
Sent via pgsql-bugs mailing list (pgsql-bugs <at> postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

chhui | 11 Mar 17:55 2015
Picon

BUG #12851: Failed to initial Jackrabbit JCR Repository

The following bug has been logged on the website:

Bug reference:      12851
Logged by:          Harry Hui
Email address:      chhui <at> ps.asl.com.hk
PostgreSQL version: 9.4.0
Operating system:   Fedora 20 x86 64Bit
Description:        

I had set up PostgreSQL 9.4 DBR version on Fedora 20. There are two
instances of PostgreSQL to perform the replication. This function was
working fine. However, I started a Jackrabbit JCR repository with
persistence manager
[org.apache.jackrabbit.core.persistence.bundle.PostgreSQLPersistenceManager].
It could not start with PostgreSQL DBR. 
It throw exception below. This exception only happened in DBR version.
Normal PostgreSQL 4.0 is working fine with Jackrabbit.
11.03.2015 11:12:48 DEBUG localhost-startStop-1 [StatManager.init:48]
Started StatManager. QueryStat is enabled false
11.03.2015 11:12:48 INFO  localhost-startStop-1 [RepositoryImpl.<init>:256]
Starting repository...
11.03.2015 11:13:06 ERROR localhost-startStop-1
[ConnectionHelper$RetryManager.doTry:548] Failed to execute SQL (stacktrace
on DEBUG log level): org.postgresql.util.PSQLException: ERROR: Cannot UPDATE
table repository_fsentry because it does not have primary key.
  Hint: Add primary key to the table
11.03.2015 11:13:06 DEBUG localhost-startStop-1
[ConnectionHelper$RetryManager.doTry:549] Failed to execute SQL
org.postgresql.util.PSQLException: ERROR: Cannot UPDATE table
repository_fsentry because it does not have primary key.
(Continue reading)

wnordmann | 11 Mar 17:35 2015
Picon
Picon

BUG #12850: ANALYZE of big table is taking extreemly much memory

The following bug has been logged on the website:

Bug reference:      12850
Logged by:          walter nordmann
Email address:      wnordmann <at> gmx.de
PostgreSQL version: 9.4.1
Operating system:   Ubuntu 14.4 LTS
Description:        

Vacuuming a really big table (139.000.000 records, 66GB tablespace, one
GIN-INDEX of 135 GB!) is consuming extreemly much memory. Much, much more
then maintenance_work_mem (2GB). at this time about 85 GB of virt mem.

see post "autovacuum worker running amok - and me too" at postgresql-general
or ask me for more data. this form is to small for it.

regards
walter

--

-- 
Sent via pgsql-bugs mailing list (pgsql-bugs <at> postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

a.g.nienhuis | 9 Mar 21:51 2015
Picon
Gravatar

BUG #12845: The GB18030 encoding doesn't support Unicode characters over 0xFFFF

The following bug has been logged on the website:

Bug reference:      12845
Logged by:          Arjen Nienhuis
Email address:      a.g.nienhuis <at> gmail.com
PostgreSQL version: 9.3.5
Operating system:   Ubuntu Linux
Description:        

Step to reproduce:

In psql:

arjen=> select convert_to(chr(128512), 'GB18030');

Actual output:

ERROR:  character with byte sequence 0xf0 0x9f 0x98 0x80 in encoding "UTF8"
has no equivalent in encoding "GB18030"

Expected output:

 convert_to
------------
 \x9439fc36
(1 row)

--

-- 
Sent via pgsql-bugs mailing list (pgsql-bugs <at> postgresql.org)
To make changes to your subscription:
(Continue reading)

mage | 9 Mar 10:12 2015
Picon

BUG #12843: pg_dump -O inserts four unwanted lines to the end of the dump

The following bug has been logged on the website:

Bug reference:      12843
Logged by:          Péter Mózes Merl
Email address:      mage <at> mage.li
PostgreSQL version: 9.3.0
Operating system:   Any
Description:        

It affects many versions.

The manual says about -O:

"To make a script that can be restored by any user, but will give that user
ownership of all the objects, specify -O."

This actually does not work because there are four lines inserted at the end
of the dump:

REVOKE ALL ON SCHEMA public FROM PUBLIC;
REVOKE ALL ON SCHEMA public FROM postgres;
GRANT ALL ON SCHEMA public TO postgres;
GRANT ALL ON SCHEMA public TO PUBLIC;

The problem is that the source and the target system might have different
users. Usually they do when we deploy Rails.

Not to forget that Linux distributions have different default user than the
one created in FreeBSD (postgres vs pgsql).

(Continue reading)

Jean-Pierre Pelletier | 7 Mar 04:24 2015
Picon

Cluster set to French_France when French_Canada selected in 9.4.1 x64 Windows Installer

Hi,
 
The Cluster created by the 9.4.1 x64 Windows Installer is set to French_France when French_Canada is selected.

Our workaround is to delete the cluster created by the installer and recreate one with initdb –encoding=UTF-8 –lc-collate=French_Canada –lc-ctype=French_Canada.

We've got that problem on both Windows 7 & 8.1.
 
Jean-Pierre Pelletier
pgriboval | 5 Mar 09:41 2015
Picon

BUG #12830: postgres-9.4 upgrade is missing PGPORT

The following bug has been logged on the website:

Bug reference:      12830
Logged by:          postgres-9.4 upgrade is missing PGPORT
Email address:      pgriboval <at> yahoo.fr
PostgreSQL version: 9.4.1
Operating system:   Centos 6.5
Description:        

In /etc/init.d/postgresql-9.4 there is no more PGPORT defined.

You can read this comment in the script:

# Version 9.4.0 Devrim Gunduz
# Remove PGPORT variable.

But bellow this command requires the PGPORT var to be set otherwise the
upgrade script does not work

NEWPGPORT=`sed -n 's/^PGPORT=//p' /etc/init.d/postgresql-$PGMAJORVERSION`

workaround is to set back PGPORT=5433, run the upgrade script and remove the
PGPORT variabla in the script

--

-- 
Sent via pgsql-bugs mailing list (pgsql-bugs <at> postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

suman.c | 6 Mar 09:01 2015

BUG #12836: pljava.dll for postgres 9.4.1-64 bit

The following bug has been logged on the website:

Bug reference:      12836
Logged by:          suman
Email address:      suman.c <at> idealinvent.com
PostgreSQL version: 9.4.1
Operating system:   windows 8 - 64 bit, jre1.6 - 64 bit
Description:        

Hi Team,

How to install pljava in Postgres 9.4.1 and please share the required files
or URL  where we can download the files.

Thanks & Regards
Suman
+919739024066

--

-- 
Sent via pgsql-bugs mailing list (pgsql-bugs <at> postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

Elena Fernandez Carmona | 5 Mar 11:27 2015
Picon

compatibilty postgres 9.2 RHEL 6.4

Hi,

 

I have Postgres 9.2.4 installed on a RHEL 5.5

I am going to migrate the operating system version to RHEL 6.4, and I would like to know if it is compatible with my postgres 9.2.4.

The only information I have found is on the following url:

http://www.postgresql.org/docs/9.2/static/supported-platforms.html

 

I would also like to know, in case the versions are compatible, if it is necessary to relink the postgres libraries?

 

Thank you very much!

 

Regards,

 

Elena Fernández, DBA, Departamento de Servicios IT

C/ Ribera del Loira 52,  28042, Madrid

T +34 913244965 F +34 915852547  E efernandezca <at> sanitas.es W sanitas.es

Sanitas, parte de Bupa

 




ADVERTENCIA:
Este mensaje o comunicación, su contenido y sus archivos adjuntos son
confidenciales y están exclusivamente dirigido al usuario o usuarios de
destino. Si por un error de envío o transmisión ha recibido este mensaje
y usted no es el destinario final, no está autorizado a usar, imprimir,
copiar o difundir este mensaje bajo ningún concepto, agradeciéndole
que proceda de inmediato a la destrucción del mismo y nos comunique esta incidencia por esta misma via.
Asimismo cualquier acción tomada o dejada de tomar basada en la información
contenida en este mensaje queda prohibida y puede ser ilegal.

WARNING:
The information, contents and attachments of this email are confidential and
are exclusively addressed to addressee or addresses stated. If you have received
this message by mistake or failure in transmission and you are not the
intended recipient, you are not allowed to use, print, copy or distribute
this message under any circumstances, please immediately destroy and inform us about it by this same mean .
Likewise, any action taken or omitted with respect to the information
in this message is prohibited and may be unlawful.

Gmane