rostap | 3 Jul 05:31 2013

BUG #8278: psql describe table

The following bug has been logged on the website:

Bug reference:      8278
Logged by:          rostap
Email address:      rostap <at> wdcarea.com
PostgreSQL version: 9.2.4
Operating system:   mac os x
Description:        

describe table does not list tables with the same names in different
schemas. only one table is being listed while the search_path is set
properly.

--

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

nunojlc | 3 Jul 00:09 2013
Picon

BUG #8277: error in instalation

The following bug has been logged on the website:

Bug reference:      8277
Logged by:          Nuno Carvalho
Email address:      nunojlc <at> hotmail.com
PostgreSQL version: 9.2.4
Operating system:   windows 8 64 bit
Description:        

good night, I can not install postgres on windows 8 64 bit whenever an error

--

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

valeriy.smirnov | 2 Jul 10:32 2013
Picon

BUG #8276: Can't install PostgreSQL with russian name for OS user

The following bug has been logged on the website:

Bug reference:      8276
Logged by:          Valery
Email address:      valeriy.smirnov <at> itv.ru
PostgreSQL version: 9.2.2
Operating system:   Windows 7
Description:        

I have russian letters in operating system user name.
During default PostgreSQL install I received installation error: Problem
running post-install step.
In installation log I found following errors: Failed to initialise the
database cluster with initdb.

--

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

rushabh.lathia | 2 Jul 06:59 2013
Picon

BUG #8275: Updateable View based on inheritance (partition) throws Error on INSERT Statement

The following bug has been logged on the website:

Bug reference:      8275
Logged by:          Rushabh Lathia
Email address:      rushabh.lathia <at> gmail.com
PostgreSQL version: 9.2.4
Operating system:   All
Description:        

View based on inheritance throws error on insert statement.

Testcase:

DROP TABLE tp_sales cascade;

CREATE TABLE tp_sales
(
salesman_id INT4, 
salesman_name VARCHAR,
sales_region VARCHAR,
sales_amount INT4
);

create table tp_sales_p_india ( check (sales_region = 'INDIA')) inherits
(tp_sales);
create table tp_sales_p_rest (check (sales_region != 'INDIA')) inherits
(tp_sales);

CREATE OR REPLACE FUNCTION tp_sales_insert_trigger()
RETURNS TRIGGER AS $$
(Continue reading)

andrew | 1 Jul 17:00 2013
Picon

BUG #8274: Wildly insane boolean selectivity estimates

The following bug has been logged on the website:

Bug reference:      8274
Logged by:          Andrew Gierth
Email address:      andrew <at> tao11.riddles.org.uk
PostgreSQL version: 9.1.9
Operating system:   any
Description:        

The guy on IRC who ran into this one was using 9.1.9, but it seems to still
exist in master.

The handling of freq_null for estimating IS NOT TRUE/FALSE for boolean
columns which are all null or almost all null (enough that analyze doesn't
find any non-null values to put in MCV) is completely off in the weeds.

Suggested fix at:

https://gist.github.com/RhodiumToad/5901567

--

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

levertond | 1 Jul 12:43 2013

BUG #8273: Assertion failure in 9.3 beta2 with serializable and savepoints

The following bug has been logged on the website:

Bug reference:      8273
Logged by:          David Leverton
Email address:      levertond <at> googlemail.com
PostgreSQL version: Unsupported/Unknown
Operating system:   RHEL 5 x86_64 
Description:        

The following test case causes a backend assertion failure in 9.3 beta2:

START TRANSACTION ISOLATION LEVEL SERIALIZABLE;
CREATE TABLE testing(
  x INTEGER PRIMARY KEY
);
INSERT INTO testing VALUES(1);
SELECT * FROM testing WHERE x = 1 FOR UPDATE;
SAVEPOINT test;
UPDATE testing SET x = 2 WHERE x = 1;
ROLLBACK TO test;
UPDATE testing SET x = 3 WHERE x = 1;
ROLLBACK;

TRAP: FailedAssertion("!(((xid) != ((TransactionId) 0)))", File:
"predicate.c", Line: 3936)

Postgres was installed using the RPMs from http://yum.pgrpms.org/, and is
using a near-default configuration (changes to port number, data directory
and pg_hba.conf, and some roles created, but nothing likely to influence
this bug).
(Continue reading)

emesika | 30 Jun 23:41 2013
Picon

BUG #8272: Unable to connect to diffrent schema from jdbc

The following bug has been logged on the website:

Bug reference:      8272
Logged by:          Eli Mesika
Email address:      emesika <at> redhat.com
PostgreSQL version: 8.4.17
Operating system:   Linux (Fedora 18)
Description:        

Hi
Postgres does not support currently defining the schema in teh connection
parameters which makes it imposible to seprate the database to several
schemas and connect to the right one from the application.

There is already a thread discussing that and a suggested patch that is
fixing that.
See

http://www.postgresql.org/message-id/4873F034.8010301 <at> scharp.org

--

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

Craig Ringer | 1 Jul 01:51 2013

Installer: Spurious "service account ... not removed" on uninstall

Hi folks

A Stack Overflow user noticed that the EDB installer for PostgreSQL
emits the message:

"The data directory (bla bla....) and service user account (NT
AUTHORITY\NetworkService) have not been removed"

when 9.2 is uninstalled. They were quite confused by this. It occurs to
me that if the standard NetworkService account is used, it'd be good to
suppress the user account not removed part of the message entirely.

http://stackoverflow.com/q/17394116/398670

-- 
 Craig Ringer                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

--

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

emre | 30 Jun 12:43 2013

BUG #8271: Configure warning: sys/ucred.h: present but cannot be compiled

The following bug has been logged on the website:

Bug reference:      8271
Logged by:          Emre Hasegeli
Email address:      emre <at> hasegeli.com
PostgreSQL version: 9.1.9
Operating system:   OpenBSD 5.3 amd64
Description:        

Configure warning on OpenBSD 5.3:

checking sys/ucred.h usability... no
checking sys/ucred.h presence... yes
configure: WARNING: sys/ucred.h: present but cannot be compiled
configure: WARNING: sys/ucred.h:     check for missing prerequisite
headers?
configure: WARNING: sys/ucred.h: see the Autoconf documentation
configure: WARNING: sys/ucred.h:     section "Present But Cannot Be
Compiled"
configure: WARNING: sys/ucred.h: proceeding with the preprocessor's result
configure: WARNING: sys/ucred.h: in the future, the compiler will take
precedence
configure: WARNING:     ## ---------------------------------------- ##
configure: WARNING:     ## Report this to pgsql-bugs <at> postgresql.org ##
configure: WARNING:     ## ---------------------------------------- ##
checking for sys/ucred.h... yes

It appears on 9.1.9, 9.2.4, 9.3beta2; does not appear on 9.0.13.

--

-- 
(Continue reading)

eyal.kaspi | 29 Jun 00:12 2013

BUG #8269: the recovery_target_inclusive is always considered as false

The following bug has been logged on the website:

Bug reference:      8269
Logged by:          PITR Recovery by timestamp ignores recovery_target_inclusive
Email address:      eyal.kaspi <at> delphix.com
PostgreSQL version: 9.2.4
Operating system:   RHEL
Description:        

While doing Point-in-time recovery and specifying a timestamp as the target,
I noticed that the timestamp is always considered as exclusive (as if
recovery_target_inclusive was set to false), i.e the recovery process will
always stop before the timestamp and never after. Example:

$cat recovery.conf:
restore_command = 'cp ../archive/%f %p 2>/dev/null'
recovery_target_time = '2013-06-27 17:40:10-0700'
recovery_target_inclusive = true

after recovery in the postgres log file:
...
LOG:  starting point-in-time recovery to 2013-06-27 17:40:10-07
LOG:  restored log file "000000010000002B000000A7" from archive
...
LOG:  recovery stopping before commit of transaction 1962, time 2013-06-27
17:40:15.849203-07
LOG:  redo done at 2B/B0004098
LOG:  last completed transaction was at log time 2013-06-27
17:39:59.047882-07
LOG:  selected new timeline ID: 2
(Continue reading)

yjxiao | 28 Jun 20:52 2013
Picon

BUG #8268: select * from pg_stat_all_tables ; ERROR: bigint out of range

The following bug has been logged on the website:

Bug reference:      8268
Logged by:          Yunong Xiao
Email address:      yjxiao <at> gmail.com
PostgreSQL version: 9.2.4
Operating system:   Solaris/Smartos
Description:        

Hi,

We've got an instance of postgresql 9.2.4 running under load in production.
We routinely run select * from pg_stat_all_tables; to check the vacuum
stats. However, this morning we noticed some performance issues with
postgresql, and upon running that query, we're getting "ERROR: bigint out of
range".

This is rather troubling, a cursory google search has revealed nothing
relevant. We also don't think we're over the BIGINT on any of the stats in
that table.

--

-- 
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