lock problem

Started by marcelo Cortezover 20 years ago3 messagesgeneral

Jump to latest

marcelo Cortez

jmdc_marcelo@yahoo.com.ar

over 20 years ago

Richard

Sorry for the delay.

question, the select * from pg_stat_activity
thows

datid|datname|procpid|usesysid|usename|current_query|query_start
52800|"sume"|30124|1|"postgres"|"<IDLE>"|"2005-09-01
13:30:02.921844-03"
52800|"sume"|30125|1|"postgres"|"<IDLE>"|"2005-09-01
13:37:21.631802-03"
52800|"sume"|30186|1|"postgres"|"SELECT
c.actuacion_car AS c_actuacion, c.comentario1 || ' '
|| c.comentario2 || ' ' || c.comentario3 AS
c_comentario FROM caratult AS c INNER JOIN extractt AS
t1 ON (c.id_extracto_car = t1.id_extracto) INNER JOIN
repartit AS r1 ON (c.id_reparticion_uc =
r"|"2005-09-01 13:35:45.152586-03"

and the select * from pg_locks

relation|database|transaction|pid|mode|granted
53046|52800||30186|"AccessShareLock"|t
||159274343|30125|"ExclusiveLock"|t
73744|52800||30186|"AccessShareLock"|t
16759|52800||30125|"AccessShareLock"|t
53094|52800||30186|"AccessShareLock"|t
73770|52800||30186|"AccessShareLock"|t
||159274288|30186|"ExclusiveLock"|t
73824|52800||30186|"AccessShareLock"|t
53054|52800||30186|"AccessShareLock"|t
73726|52800||30186|"AccessShareLock"|t
53074|52800||30186|"AccessShareLock"|t
53049|52800||30186|"AccessShareLock"|t
53127|52800||30186|"AccessShareLock"|t
9567503|52800||30186|"AccessShareLock"|t
74274|52800||30186|"AccessShareLock"|t

this queries show locks into 30816 pid or a'im wrong?
best regards
MDC

 --- Richard Huxton <dev@archonet.com> escribiï¿½:

marcelo Cortez wrote:

Hi Richard , folks

the query is:

SELECT c.actuacion_car AS c_actuacion,
c.comentario1 || ' ' || c.comentario2 || ' ' ||
c.comentario3 AS c_comentario
FROM caratult AS c INNER JOIN extractt AS t1 ON

...etc

I'm not seeing anything here that should take locks,
although it's late
where I am.

without table definition etc, you see are selects
only.
during this query, select * from

pg_catalog.pg_locks

show many rows with exclusive locks , and other
activities or user's be freezed,

Are you *sure* that it's this query? Could you show
some of the rows
from pg_locks along with corresponding rows from
pg_stat_activity?

--
Richard Huxton
Archonet Ltd

---------------------------(end of
broadcast)---------------------------
TIP 5: don't forget to increase your free space map
settings

__________________________________________________
Correo Yahoo!
Espacio para todos tus mensajes, antivirus y antispam ï¿½gratis!
ï¿½Abrï¿½ tu cuenta ya! - http://correo.yahoo.com.ar

marcelo Cortez

jmdc_marcelo@yahoo.com.ar

over 20 years ago

In reply to: marcelo Cortez (#1)

Re: lock problem

hi Richard ,folks

Question: is normal this locks ?
which is the reason of this?
thanks for your time
best regards
MDC

 --- Richard Huxton <dev@archonet.com> escribiï¿½:

marcelo Cortez wrote:

Richard

Sorry for a delay

question the select * from pg_stat_activity
thows

52800|"sume"|30124|1|"postgres"|"<IDLE>"|"2005-09-01

13:30:02.921844-03"

52800|"sume"|30125|1|"postgres"|"<IDLE>"|"2005-09-01

13:37:21.631802-03"
52800|"sume"|30186|1|"postgres"|"SELECT
c.actuacion_car AS c_actuacion, c.comentario1 || '

'

|| c.comentario2 || ' ' || c.comentario3 AS
c_comentario FROM caratult AS c INNER JOIN

extractt AS

t1 ON (c.id_extracto_car = t1.id_extracto) INNER

JOIN

repartit AS r1 ON (c.id_reparticion_uc =
r"|"2005-09-01 13:35:45.152586-03"

and the select * from pg_locks
relation|database|transaction|pid|mode|granted
53046|52800||30186|"AccessShareLock"|t
||159274343|30125|"ExclusiveLock"|t
73744|52800||30186|"AccessShareLock"|t
16759|52800||30125|"AccessShareLock"|t
53094|52800||30186|"AccessShareLock"|t
73770|52800||30186|"AccessShareLock"|t
||159274288|30186|"ExclusiveLock"|t
73824|52800||30186|"AccessShareLock"|t
53054|52800||30186|"AccessShareLock"|t
73726|52800||30186|"AccessShareLock"|t
53074|52800||30186|"AccessShareLock"|t
53049|52800||30186|"AccessShareLock"|t
53127|52800||30186|"AccessShareLock"|t
9567503|52800||30186|"AccessShareLock"|t
74274|52800||30186|"AccessShareLock"|t

this queries show locks into 30816 pid or a'im

wrong?

That's right - pid=30816 is the backend running the
SELECT
c.actuacion_car... query (see the pg_stat_activity
output).

The only other locks mentioned are for pid=30125,
which I think are
where you're executing "SELECT * FROM pg_locks" -
bit puzzled as to why
the relation/database columns are blank though.

In short - I can't see anything blocking your query.
What error message
was telling you that locks were causing a problem?

--
Richard Huxton
Archonet Ltd

________________________________________________
ï¿½Llamï¿½ y ganï¿½!
Usï¿½ Yahoo! Messenger con Voz y participï¿½ del sorteo de un pasaje a cualquier lugar del mundo.
Inscribite aquï¿½: http://messenger.yahoo.com/ar/

Import Notes

Reply to msg id not found: 4317FF63.5070309@archonet.com | Resolved by subject fallback

Richard Huxton

dev@archonet.com

over 20 years ago

In reply to: marcelo Cortez (#2)

Re: lock problem

marcelo Cortez wrote:

hi Richard ,folks

Question: is normal this locks ?
which is the reason of this?

As I said - I don't see any locks that could cause you problems. Can you
provide the error message showing locks timing out?

--
Richard Huxton
Archonet Ltd