In an interesting twist, we tried to drop the table in question and got
this:
-bash-3.2$ dropdb exomeSNP
dropdb: database removal failed: ERROR: database "exomeSNP" is being
accessed by other users
DETAIL: There are 1 prepared transaction(s) using the database.
-bash-3.2$
So, it seems that
On Thu, Aug 9, 2012 at 4:58 AM, Tom Lane wrote:
> Brian McNally writes:
>> Ok, I'm running with all available updates and kernel 2.6.18-308.4.1.el5
>> but am still having the same problem.
>
> It's fairly clearly blocked on a lock ... have you looked into the
> pg_locks view to see what is holdin
Brian McNally writes:
> Ok, I'm running with all available updates and kernel 2.6.18-308.4.1.el5
> but am still having the same problem.
It's fairly clearly blocked on a lock ... have you looked into the
pg_locks view to see what is holding the lock?
(I'm wondering about a prepared transaction,
Ok, I'm running with all available updates and kernel 2.6.18-308.4.1.el5
but am still having the same problem.
--
Brian McNally
On 08/07/2012 05:29 PM, Sergey Konoplev wrote:
On Wed, Aug 8, 2012 at 4:27 AM, Brian McNally wrote:
RHEL 5.7 on both. 2.6.18-274.el5 on the system that works,
2.6.1
It took me a little while but here it is. Let me know if this is helpful
or not. I'm not sure if I need more -debuginfo packages installed:
===
[root@gvsdb-dev tmp]# gdb /usr/pgsql-9.0/bin/postmaster 1160
GNU gdb (GDB) Red Hat Enterprise Linux (7.0.1-32.el5_6.2)
Copyright (C) 2009 Free Software
On Wed, Aug 8, 2012 at 3:03 AM, Brian McNally wrote:
> [root@gvsdb-dev tmp]# gdb /usr/pgsql-9.0/bin/postmaster 1160
> GNU gdb (GDB) Red Hat Enterprise Linux (7.0.1-32.el5_6.2)
> (gdb) bt
> #0 0x00378f8d5497 in semop () from /lib64/libc.so.6
> #1 0x005bc1c3 in PGSemaphoreLock (sema=0x
Hi Brian,
On Wed, Aug 1, 2012 at 10:21 PM, Brian McNally wrote:
> I was able to upgrade Postgres to 9.0.8 today and the ALTER TABLE... command
> still hangs. Stracing the hung PID doesn't reveal much:
>
> [root@gvsdb-dev ~]# strace -fp 13107
> Process 13107 attached - interrupt to quit
> semop(84
On Wed, Jul 18, 2012 at 9:42 PM, Brian McNally wrote:
> I don't get any rows returned back from that query. I'm running it while
> connected to the DB in question. Am I supposed to substitute values for any
Try this one. Are there any COPY queries (current_query) or long
lasting transactions (age
Hi Raghu,
I don't get any rows returned back from that query. I'm running it while
connected to the DB in question. Am I supposed to substitute values for
any of the variables in the query?
--
Brian McNally
On 07/17/2012 07:23 PM, raghu ram wrote:
On Wed, Jul 18, 2012 at 1:24 AM, Brian M
On Wed, Jul 18, 2012 at 1:24 AM, Brian McNally wrote:
> Hello,
>
> I'm running Postgres 9.0.2 on RHEL 5.6 x86_64 and trying to run the
> following statement:
>
> alter table samples add column in_esp1234 text;
>
> When I do this the command just hangs. ps output indicates that it's
> waiting:
>
>
Hello,
I'm running Postgres 9.0.2 on RHEL 5.6 x86_64 and trying to run the
following statement:
alter table samples add column in_esp1234 text;
When I do this the command just hangs. ps output indicates that it's
waiting:
postgres: postgres exomeSNP [local] ALTER TABLE waiting
When I look
11 matches
Mail list logo