Scot Kreienkamp writes:
> There's something wrong with the query that I've written based on what you
> gave me.
It looks like you forgot the ON condition for the next-to-last JOIN,
so the parser is still expecting another ON when it runs into the WHERE.
Personally I think this sort of FROM cons
g something in one of the joins.
Thanks!
Scot Kreienkamp
Senior Systems Engineer
skre...@la-z-boy.com
-Original Message-
From: Tom Lane [mailto:t...@sss.pgh.pa.us]
Sent: Monday, January 30, 2012 9:49 PM
To: Scot Kreienkamp
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] list b
Scot Kreienkamp writes:
> My apologies for the slightly novice post on this, but I'm a bit stumped. I
> have this query that I found on the net and adapted a little to find the
> queries that were blocking:
> "select bl.pid as \"Blocked PID\", a.usename as \"Blocked User\", kl.pid as
> \"Bloc
Hey everyone,
My apologies for the slightly novice post on this, but I'm a bit stumped. I
have this query that I found on the net and adapted a little to find the
queries that were blocking:
"select bl.pid as \"Blocked PID\", a.usename as \"Blocked User\", kl.pid as
\"Blocking PID\", ka.usena
