On Jul 8, 2009, at 3:42 PM, Tom Lane wrote:
Joe Uhl writes:
On Jul 8, 2009, at 3:00 PM, Tom Lane wrote:
Hmm. In any case that shouldn't have led to a lock left hanging.
Assuming that it was a regular and not autovacuum, do you know what
the exact command would have been? (In parti
On Jul 8, 2009, at 3:00 PM, Tom Lane wrote:
Joe Uhl writes:
On Jul 8, 2009, at 2:41 PM, Tom Lane wrote:
What exactly did you do to "kill" those processes? Do you remember
whether any of them happened to have PID 10453?
I used "kill pid1 pid2 pid3 ..." (no -9) as root.
On Jul 8, 2009, at 2:41 PM, Tom Lane wrote:
Joe Uhl writes:
I had to bounce an OpenMQ broker this morning (this database is the
DB
for an OpenMQ HA setup) and couldn't get it to reconnect to postgres.
On inspecting the database I found dozens of vacuum processes waiting
(I have a cro
or everything including our main product
database (hundreds of transactions/sec, 100's of GB of data) for years
and have never seen this scenario.
Any help is appreciated, I can easily provide any additional
information that may be helpful.
Joe Uhl
--
Sent via pgsql-bugs mailing lis
Possibly, I saw that thread but may not have dug into the content
deeply enough. My apologies if this is the case, i'll check it out
further.
On Sep 10, 2008, at 3:38 PM, Tom Lane wrote:
Joe Uhl <[EMAIL PROTECTED]> writes:
We have a query that returns a different result i
We have a query that returns a different result in 8.2.5 and 8.3.0.
This is the query, I apologize for the names and aliases, it is
hibernate-generated.
select * from action_items actionitem0_
left outer join action_item_states states1_ on
actionitem0_.id=states1_.action_item_id
where (
