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

ddebernardy | 28 Jun 00:11 2013
Picon

BUG #8266: Problem with \d and ::regclass when tables have utf8 chars in their name

The following bug has been logged on the website:

Bug reference:      8266
Logged by:          Denis de Bernardy
Email address:      ddebernardy <at> yahoo.com
PostgreSQL version: 9.2.4
Operating system:   OSX Lion
Description:        

As identified in this StackOverflow thread:

http://stackoverflow.com/questions/17353469/postgresql-and-unicode-table-names-why-can-i-not-select-the-table-name-from-the/

---

# create table pinkƒpink1 (id serial);
NOTICE:  CREATE TABLE will create implicit sequence "pink?pink1_id_seq" for
serial column "pink?pink1.id"
CREATE TABLE
# select 'pinkƒpink1'::name;
    name    
------------
 pinkƒpink1
(1 row)

# select 'pinkƒpink1'::regclass;
  regclass   
-------------
 "pinkpink1"
(1 row)
(Continue reading)

daniel.degasperi | 27 Jun 17:26 2013

BUG #8260: problem with sequence and tablename

The following bug has been logged on the website:

Bug reference:      8260
Logged by:          Daniel Degasperi
Email address:      daniel.degasperi <at> r3-gis.com
PostgreSQL version: 9.1.7
Operating system:   Centos 6.4
Description:        

I've created a table:

CREATE TABLE t23456789012345678901234567890123456789012345678901
(
  t1234_id serial,
  PRIMARY KEY (t1234_id)
)
WITH (
  OIDS=FALSE
);

This generated the sequence:

CREATE SEQUENCE
t2345678901234567890123456789012345678901234567890_t1234_id_seq
  INCREMENT 1
  MINVALUE 1
  MAXVALUE 9223372036854775807
  START 1
  CACHE 1;

(Continue reading)

varunkarkala | 27 Jun 14:23 2013
Picon

BUG #8259: Not able to search composite type in search object

The following bug has been logged on the website:

Bug reference:      8259
Logged by:          Varun
Email address:      varunkarkala <at> gmail.com
PostgreSQL version: 9.2.4
Operating system:   Win 7
Description:        

Hello,

NOt able to search composite type in search object

Ragrds

--

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

varunkarkala | 27 Jun 11:14 2013
Picon

BUG #8258: I am not able to search composite types in search object

The following bug has been logged on the website:

Bug reference:      8258
Logged by:          Varun
Email address:      varunkarkala <at> gmail.com
PostgreSQL version: 9.2.4
Operating system:   Windows 7
Description:        

hello,
object
Regards

--

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

Kristopher Kane | 27 Jun 03:55 2013
Picon

BUG #8238: duplicate of bug #6372 on panffs

Sorry to replay in this way but I just joined the list based on a
thread I found from a few days ago.  I hit the panfs fsync problem
this morning and it appears the same as what Jim Hughes is reporting.
Initially thought it was SELinux (RHEL 6.4) but it persisted after I
turned it off.

Bug #6372 and Jim's reply reference a patch for copydir.c but I don't
see a patch.  It might have been an attachment that I didn't see
through the archives.  Is this patch available with instructions for
compilation?

Thanks,

Kris

--

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

lalbin | 27 Jun 01:43 2013

BUG #8257: Multi-Core Restore fails when containing index comments

The following bug has been logged on the website:

Bug reference:      8257
Logged by:          Lloyd Albin
Email address:      lalbin <at> fhcrc.org
PostgreSQL version: 9.2.4
Operating system:   SUSE Linux (64-bit)
Description:        

I have found the restore will fail when using pg_restore's -j option, with
more than one core, on a dump that contains a COMMENT INDEX.

I have tried this using both Postgres 9.0.12 & 9.2.4

I have created a test case that shows the problem.

Create a database called test_db.

CREATE DATABASE test_db
  WITH OWNER = postgres
    ENCODING = 'UTF8'
    TEMPLATE = template0;

Run this next section to add the table, index, and index comment to the
test_db database.

CREATE TABLE public.tbl_test (
  pkey TEXT NOT NULL,
  CONSTRAINT tbl_test_pkey PRIMARY KEY(pkey)
);
(Continue reading)

dmcmillan | 26 Jun 17:25 2013

BUG #8256: query screen on pgAdmin is show blank

The following bug has been logged on the website:

Bug reference:      8256
Logged by:          Dan
Email address:      dmcmillan <at> snapadvances.com
PostgreSQL version: 9.2.4
Operating system:   Mac OS version 10.8.4
Description:        

pgadmin 1.16.1

java version "1.7.0_21"
Java(TM) SE Runtime Environment (build 1.7.0_21-b12)
Java HotSpot(TM) 64-Bit Server VM (build 23.21-b01, mixed mode)

distribution postgresql-9.2.4-1-osx.dmg

The query window had 3 areas, the scratch area, the main sql area and the
results area. The only pane that shows up for me is the scratch pane. 

It was working when I installed it initially. I didn't make any changes and
do not believe I updated any os software (although I could be mistaken
there). It stopped working about 3 days ago as far as I can tell.

--

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

(Continue reading)

gabriel.ct | 26 Jun 14:21 2013
Picon

BUG #8255: encoding latin1

The following bug has been logged on the website:

Bug reference:      8255
Logged by:          gabriel
Email address:      gabriel.ct <at> santamonicace.com.br
PostgreSQL version: 8.4.4
Operating system:   windows xp
Description:        

Good afternoon, I live in Brazil and I need to create a database with
encoding LATIN1. how can I make this database. I use windows xp and
postgreSQL. please send a tutorial on how to makeThank 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


Gmane