hi Richard ,folks
Question: is normal this locks ?
which is the reason of this?
thanks for your time
best regards
MDC
--- Richard Huxton <dev@xxxxxxxxxxxx> escribió:
> marcelo Cortez wrote:
> > Richard
> >
> > Sorry for a 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?
>
> 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/
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
