jaroslav.potapov | 10 Jul 21:07 2013
Picon

BUG #8293: There are no methods to convert json scalar text to text in v9.3 beta2

The following bug has been logged on the website:

Bug reference:      8293
Logged by:          Yaroslav Potapov
Email address:      jaroslav.potapov <at> gmail.com
PostgreSQL version: Unsupported/Unknown
Operating system:   All
Description:        

SELECT '"a\"b"'::json::text

returns text: '"a\"b"' ,
but it must return 'a"b' in my opinion.

Thank you.

--

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

renzo_gch | 10 Jul 18:51 2013
Picon

BUG #8292: Error en Una Función llamada desde NetBeans

The following bug has been logged on the website:

Bug reference:      8292
Logged by:          Renzo Carranza
Email address:      renzo_gch <at> hotmail.com
PostgreSQL version: 9.2.3
Operating system:   Windows
Description:        

Este es mi error "malformed function or procedure escape syntax at offset
6"

Estas son mis funciones con las que hago la transacción en Java NetBeans 

CREATE OR REPLACE FUNCTION fu_ingresaralquiler()
  RETURNS integer AS
$BODY$
DECLARE
lalquilercodigo integer;
BEGIN
	INSERT INTO alquiler(vigencia) 
		VALUES (true::boolean);
	lalquilercodigo = CURRVAL('alquiler_codigo_seq');
     return lalquilercodigo;
END;
$BODY$
  LANGUAGE 'plpgsql'

CREATE OR REPLACE FUNCTION fu_insertardetallealquiler( pnumero integer,
pnombres character varying, papellidos character varying, pcodigohabitacion
(Continue reading)

lalbin | 10 Jul 00:05 2013

BUG #8291: postgres_fdw does not re-read USER MAPING after change.

The following bug has been logged on the website:

Bug reference:      8291
Logged by:          Lloyd Albin
Email address:      lalbin <at> fhcrc.org
PostgreSQL version: Unsupported/Unknown
Operating system:   Windows 7 (64-bit)
Description:        

Tested on
Windows 7 (64-bit) Postgres 9.3.0 Beta 2  -> Windows 7 (64-bit) Postgres
9.3.0 Beta 2
Windows 7 (64-bit) Postgres 9.3.0 Beta 1 -> SUSE Linux (64-bit) Postgres
9.0

I have found that if you change the password in the USER MAPPING, that
postgres_fdw will not use it unless the current password fails or you close
and re-open your postgres connection. I found this while testing to see if
the USER MAPPING's supports MD5 passwords and they appeared to until the
next day when I found that they no longer worked because I had closed and
re-opened my connection.

The second error that I found is in the documentation of ALTER USER MAPPING.
It incorrectly says how to update a users password.

CREATE DATABASE db1
  WITH ENCODING='UTF8'
       OWNER=postgres
       CONNECTION LIMIT=-1;

(Continue reading)

pgnube | 9 Jul 18:02 2013
Picon

BUG #8290: broken/unexpected locking behavior

The following bug has been logged on the website:

Bug reference:      8290
Logged by:          pgnoob
Email address:      pgnube <at> gmail.com
PostgreSQL version: 8.4.13
Operating system:   CentOS Linux
Description:        

I experienced a db deadlock.  After tracking down the problem I attributed
it to some unusual locking behavior in postgresql where it acquires locks in
an unexpected way that contributed to the deadlock.

I sent the following information to pgsql-general to ask if it is expected
locking behavior.  The only responses that I got said that the behavior is
reproducible on 9.1 and 9.3 beta 2.
Nobody said that this is expected locking behavior and I believe it to be a
bug, so I am filing this bug report.
The exact steps on how to reproduce the problem are shown below.  Thank you
for putting together a great DB and for working on this bug report.

I'm using Postgres 8.4.13

I have two tables, call them A & B for example purposes.

Table A, with column id

Table B
  - foreign key reference a_id matches A.id FULL
  - some other columns blah1, blah2, blah3
(Continue reading)

potapov.dmitry | 9 Jul 17:05 2013
Picon

BUG #8289: pg_stat_statements incorrect query text when executing multiple queries in a single PQexec

The following bug has been logged on the website:

Bug reference:      8289
Logged by:          Dmitriy Potapov
Email address:      potapov.dmitry <at> gmail.com
PostgreSQL version: 9.2.4
Operating system:   Scientific Linux 6.3 
Description:        

pg_stat_statements view contains incorrectly normalized query texts when
executing multiple queries in a single PQexec call.

How to reproduce:
1. Create a database.
2. Populate it with pss_mq_testcase.sql 
http://pgsql.privatepaste.com/e834c641d6
3. Compile pss_mq.c http://pgsql.privatepaste.com/88421cfdf7 with following
command:
gcc -o pss_mq -I`/usr/pgsql-9.2/bin/pg_config --includedir` -L
`/usr/pgsql-9.2/bin/pg_config --libdir` -lpq pss_mq.c

4. Execute select pg_stat_statements_reset();
5. Run pss_mq with connection string to database as command line parameter
(for example: ./pss_mq 'dbname=psstest port=5433')
6. Check pg_stat_statements view. I get the following results:
http://pgsql.privatepaste.com/6908db7e80

The testcase runs five UPDATE commands with two PQexec calls.
First PQexec call runs: "UPDATE t1 SET a=101 WHERE id=0; UPDATE t1 SET a=102
WHERE id=1; UPDATE t1 SET a=103 WHERE id=2"
(Continue reading)

tgauss | 9 Jul 14:44 2013
Picon

BUG #8288: 9.3.0Beta2 - Windows Installer bug #7738 still open

The following bug has been logged on the website:

Bug reference:      8288
Logged by:          Thomas Gauss
Email address:      tgauss <at> wolfsysteme.de
PostgreSQL version: Unsupported/Unknown
Operating system:   Windows 7 64bit
Description:        

Having data directory on drive d:\database\data-9.3 it takes about 45
minutes to initialise cluster. Most of the time icacls is run by the
installer, seems like bug#7738 is still active in 9.3.0b2's installer.

--

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

Picon

yum repository

http://yum.postgresql.org/ is not accessable :(
lindebg | 6 Jul 22:41 2013
Picon

BUG #8287: select distinct / select group by - Invalid result

The following bug has been logged on the website:

Bug reference:      8287
Logged by:          Jacek
Email address:      lindebg <at> gmail.com
PostgreSQL version: 9.2.4
Operating system:   Debian x64 / Windows 8 x64
Description:        

I wanted to report an incorrect execution of the query SELECT DISTINCT... :

Example:

create table machines
(
	machineid int primary key,
	machinename varchar not null,
	editdate timestamp,
	deleted boolean
);

insert into machines(machineid, machinename, deleted, editdate) values
(1, 'test', false, null);

create table commands
(
	commandid int primary key,
	command varchar not null,
	machineid int not null references machines(machineid) on delete cascade,
	resultdate timestamp
);

insert into commands(commandid, machineid, command, resultdate) values
(1, 1, 'command1', '2011-03-25 13:40:58.430'),
(2, 1, 'command2', null),
(3, 1, 'command3', '2012-04-05 21:22:23.111'),
(4, 1, 'command1', null),
(5, 1, 'command1', '2011-04-11 23:17:09.113');

create table commandsaddit
(
	commandid int primary key references commands(commandid) on delete
cascade,
	param1 varchar,
	param2 varchar
);

create view vmachinesall
as
select
	hs.machineid,
	hs.machinename,
	hs.editdate,
	case when hs.deleted then hs.editdate else null::timestamp end as
deleteddate
from machines hs;

create view vmachines
as
select
	hs.machineid,
	hs.machinename,
	hs.editdate
from vmachinesall hs
where (hs.deleteddate is null);

create view vcommands
as
select
	t.commandid,

	case
		when (t.resultdate is null) then 'Processing'::varchar
		when (a.commandid is not null) then 'Ok 1'::varchar
		else 'Ok 2'::varchar
	end as status
from commands t inner join vmachines h on t.machineid = h.machineid
	left join commandsaddit a on t.commandid = a.commandid;

-- example:

select distinct status
from vcommands;

-- RESULT:
--   Processing
--   Ok 2

select distinct status
from vcommands
where status = 'xxx'; -- any value

-- or

select status
from vcommands
where status = 'xxx' -- any value
group by status;

-- RESULT:
--   Ok 2
--   Processing
--   Ok 2
--   Processing
--   Ok 2

--

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

eike | 5 Jul 01:11 2013
Picon

BUG #8286: severe bug in auth

The following bug has been logged on the website:

Bug reference:      8286
Logged by:          Eike Dierks
Email address:      eike <at> inter.net
PostgreSQL version: 9.2.4
Operating system:   CentOS release 6.4
Description:        

I believe to have found a severe bug in auth.
I don't want to post that here.

Please contact me.
~eike

--

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

Chad Wagner | 4 Jul 20:41 2013
Picon

Re: Stalled post to pgsql-bugs

After further testing, this test case should be refined to throw NO_DATA_FOUND errors from the INTO STRICT clause to produce the memory leak.

In pl_exec.c, exec_stmt_execsql does not free the SPI_tuptable by calling SPI_freetuptable before the ereport.  Attached is a patch to 9.2-STABLE that seems to resolve it.




Attachment (pl_exec.diff): application/octet-stream, 1212 bytes
Attachment (valgrind.out): application/octet-stream, 44 KiB

--

-- 
Sent via pgsql-bugs mailing list (pgsql-bugs <at> postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
manish.roy | 4 Jul 14:40 2013
Picon

BUG #8285: Unable to install the pgAgent

The following bug has been logged on the website:

Bug reference:      8285
Logged by:          Manish Roy
Email address:      manish.roy <at> quipment.in
PostgreSQL version: 9.2.1
Operating system:   Windows 7
Description:        

Hello,

I was trying to install the pgAgent in my windows system to create the job
in PostGreSQL.

But unfortunately the steps specified in this
"http://www.pgadmin.org/docs/1.4/pgagent-install.html" is not helping me out
in installation of agent.

It will be really grateful if  anyone can help me out in the installation of
a agent in postgresql.

Thanks

--

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


Gmane