nbuduroi | 9 Oct 19:35 2013
Picon

BUG #8515: Random 'relation "..." does not exist'

The following bug has been logged on the website:

Bug reference:      8515
Logged by:          Nicolas Buduroi
Email address:      nbuduroi <at> gmail.com
PostgreSQL version: 9.2.4
Operating system:   ArchLinux
Description:        

We've recently migrated an application from MySQL to Postgres and I've been
experiencing some really strange and random bugs. The application is a
pretty simple Rails application and the Postgres setup is the default one
provided by ArchLinux.

Basically, at some point a query, update or insert will not work and
complain about a table not existing, but that table was used without any
issue previously. Closing the running connection to the database and
reconnecting make that error disappear. Two concurrent connections (one from
a console and another from the app) could be contradicting themselves, one
giving the error and the other not.

This only happen on a development machine which is running version 9.2.4 of
Postgres. We've not encountered this error on our production/staging/ci
servers which are running Postgres 9.1.9 version.

--

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

shahtejas2811 | 9 Oct 18:24 2013
Picon

BUG #8514: cache lookup failed for relation 421062806

The following bug has been logged on the website:

Bug reference:      8514
Logged by:          Tejas
Email address:      shahtejas2811 <at> gmail.com
PostgreSQL version: 8.4.0
Operating system:   Linux 7.2 
Description:        

my postgresql running file . but sometime i found cache lookup failed for
relation 421062806 error in postgresql log. can anyone tell me significant
of this 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

tommi.korhonen | 9 Oct 14:39 2013
Picon

BUG #8513: Error recognizing data type in union

The following bug has been logged on the website:

Bug reference:      8513
Logged by:          Tommi Korhonen
Email address:      tommi.korhonen <at> thl.fi
PostgreSQL version: 8.4.17
Operating system:   Redhat Linux
Description:        

Example:

create table t1(a integer);
create table t2(b integer);
create table t3(c integer);

select null from t1
union all
select null from t2
union all
select c from t3;

produces an error

ERROR:  UNION types text and integer cannot be matched
LINE 5: select c from t3;

but 

select null from t2
union all
(Continue reading)

Dhiraj Chawla | 9 Oct 09:29 2013

Getting "getsockopt(TCP_KEEPALIVE) failed" LOG message in PG Logs on Solaris 10

Hi,

I am getting "getsockopt(TCP_KEEPALIVE) failed: Option not supported by protocol" log message in the PG Logs whenever I run a query referencing "pg_catalog.pg_settings" on Solaris 10 (both Sprac and x86-64).

You can reproduce this case by running a query like: SELECT name, setting, unit FROM pg_catalog.pg_settings;

This happens only the first time you execute the query though.

This issue was reproducible to me on both PostgreSQL 9.0.4 and PostgreSQL 9.2.4. This happens when I run the query via psql or pgAdminIII by connecting to the database server over the TCP socket (i.e. by providing host details in -h). Same behavior is not reproducible if I connect to database server over Unix Socket.

I am not sure if this has been reported before, but I thought I should bring this issue to your notice.

regards,


Dhiraj Chawla
Senior Software Engineer
EnterpriseDB Corporation
The Enterprise PostgreSQL Company

Phone: +91-20-30589522
Mátyás Milos | 8 Oct 23:57 2013
Picon

win8

Dear Support,

I would like to install the newest postgresql to win 8 but something wrong with that... At the end I got a message about some problem and I don't know why. The problem is the postgresql can not connect to the host ( 127.0.0.1 ). How can I fix it? 

Thanks!
kurt | 8 Oct 20:52 2013
Picon

BUG #8512: Can't use columns I can't read in the where clause of a select

The following bug has been logged on the website:

Bug reference:      8512
Logged by:          Kurt Roeckx
Email address:      kurt <at> roeckx.be
PostgreSQL version: 9.0.6
Operating system:   Linux
Description:        

Hi,

When I read the documentation for GRANT, I see:
SELECT

    Allows SELECT from any column, or the specific columns listed, of the
specified table, view, or sequence. Also allows the use of COPY TO. This
privilege is also needed to reference existing column values in UPDATE or
DELETE.

I read that as "SELECT field1 from table where field2 = 1" should work if I
have grant select(field1), but not on field2.  I'm getting a "permission
denied".  If I remove the where clause it of course works.

I'm not sure if the behaviour is expected or not.  Maybe I'm reading the
documentation wrong, or maybe the documentation is just wrong.  Could
someone please clarify?

Kurt

--

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

shahtejas2811 | 8 Oct 10:02 2013
Picon

BUG #8511: some of object dont drop

The following bug has been logged on the website:

Bug reference:      8511
Logged by:          Tejas
Email address:      shahtejas2811 <at> gmail.com
PostgreSQL version: Unsupported/Unknown
Operating system:   Linux
Description:        

cache lookup failed for relation 421062806 

--

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

Aditya srivastava | 6 Oct 07:50 2013
Picon

bug fixing request

sir,
I want to do bug fixing for your project.At present i am pursuing b.tech in computer science.c and c++ are the languages of my interest.
i would be very delightful if i could work for your company.
Thank you
Aditya srivastava
regards
kyrimis | 4 Oct 15:26 2013
Picon

BUG #8500: Upgrade to postgis 2.1 breaks existing databases

The following bug has been logged on the website:

Bug reference:      8500
Logged by:          Kriton Kyrimis
Email address:      kyrimis <at> alumni.princeton.edu
PostgreSQL version: 9.2.4
Operating system:   Scientific Linux 6.4
Description:        

The version of postgis, available in the postgresql yum repository for
postgis 9.2, was recently upgraded to version 2.1. This breaks existing
databases built with postgis 2.0, as queries involving postgis fail with the
error message "ERROR:  could not access file "$libdir/postgis-2.0": No such
file or directory"

This includes backing up the databases, so upgrading them to use postgis 2.1
may not even be an option, if a hard upgrade is required.

I have downgraded all postgis2_92 packages to version 2.0.4 and excluded
them from future upgrades, but I'd recommend reverting to that version in
the repositories, as well. At the very least, please ensure that version
2.0.x of the packages remains available in the future. Better still, provide
alternative postgis21_92-* packages, for those wishing to use the latest
version, without affecting those that use the previous version.

--

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

lr | 4 Oct 04:09 2013
Picon

BUG #8498: pg_trgm is missing from windows edb package

The following bug has been logged on the website:

Bug reference:      8498
Logged by:          Regina Obe
Email address:      lr <at> pcorp.us
PostgreSQL version: 9.3.0
Operating system:   Windows 2003 x 64-bit
Description:        

I noticed when restoring my 9.2 databases to 9.3 that my pg_trgm extension
is missing.  In looking it doesn't seem to be packaged with the PostgreSQL
9.3 EDB installer (at least for 64-bit) but I assume it is still a separate
extension
since it's still in separate modules section

http://www.postgresql.org/docs/9.3/static/pgtrgm.html

Am I missing something?

Sorry if this is an oversight on my part.

--

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

Andres Freund | 3 Oct 18:11 2013

abort()/segfault when starting postgres in inaccessible CWD

Hi,

Starting postgres with a CWD that's not readable will trigger an Assert
and if those are disabled it presumably will segfault.

#0  0x00007ffff75621e5 in __GI_raise (sig=sig <at> entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#1  0x00007ffff7565398 in __GI_abort () at abort.c:90
#2  0x000000000089031d in ExceptionalCondition (
    conditionName=0xa6e530 "!(((CurrentMemoryContext) != ((void *)0) && (((((const
Node*)((CurrentMemoryContext)))->type) == T_AllocSetContext))))", errorType=0xa6e2c9
"BadArgument", fileName=0xa6e240
"/home/andres/src/postgresql/src/backend/utils/mmgr/mcxt.c", lineNumber=649)
    at /home/andres/src/postgresql/src/backend/utils/error/assert.c:54
#3  0x00000000008bc206 in palloc (size=1024) at /home/andres/src/postgresql/src/backend/utils/mmgr/mcxt.c:649
#4  0x00000000006597b2 in initStringInfo (str=0x7fffffffc410) at /home/andres/src/postgresql/src/backend/lib/stringinfo.c:50
#5  0x0000000000896383 in expand_fmt_string (fmt=0xa8d3e8 "could not change directory to \"%s\": %s",
edata=0xd587e0 <errordata>)
    at /home/andres/src/postgresql/src/backend/utils/error/elog.c:3167
#6  0x0000000000892c52 in elog_finish (elevel=15, fmt=0xa8d3e8 "could not change directory to \"%s\": %s")
    at /home/andres/src/postgresql/src/backend/utils/error/elog.c:1297
#7  0x00000000008d932a in resolve_symlinks (path=0x7fffffffdad0 "/home/andres/build/postgres/dev-assert/vpath/src/backend/postgres")
    at /home/andres/src/postgresql/src/port/exec.c:293
#8  0x00000000008d8e10 in find_my_exec (argv0=0xd60bb0
"/home/andres/build/postgres/dev-assert/vpath/src/backend/postgres", 
    retpath=0x7fffffffdad0 "/home/andres/build/postgres/dev-assert/vpath/src/backend/postgres")
    at /home/andres/src/postgresql/src/port/exec.c:144
#9  0x00000000008d96aa in set_pglocale_pgservice (argv0=0xd60bb0
"/home/andres/build/postgres/dev-assert/vpath/src/backend/postgres", 
    app=0xa05440 "postgres-9.4") at /home/andres/src/postgresql/src/port/exec.c:561
#10 0x0000000000668932 in main (argc=21, argv=0xd60af0) at /home/andres/src/postgresql/src/backend/main/main.c:98

So, the problem is that we're calling set_pglocale_pgservice() which
indirectly can call elog() long before we've initialized memory
contexts.

To reproduce do something like:

# become root
su
# change into root-only directory
cd /root
# switch user, without changing directory
su postgres
# execute postgres
/path/to/postgres -D frakbar

Greetings,

Andres Freund

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


Gmane